[BUG] Survey conflicts with Claude Next Steps

[jonyoder]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

When Claude outputs a numbered list of next steps, e.g., "Would you like me to...", it accepts numeric input. While waiting for user input, Claude often also prompts for a survey with numeric options. When this happens, I usually don't even see the survey since I'm evaluating next steps, and I respond with the appropriate numeric value for next steps, inadvertently answering the survey with a random value.

What Should Happen?

Claude should evaluate its own context to decide whether prompting for numeric survey input is appropriate.

Error Messages/Logs

Steps to Reproduce

Prompt claude in a manner that will produce numeric lists of "next steps" and continue to do so until the claude survey appears.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.0.24 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

No response

[github-actions]

Found 1 possible duplicate issue:

1. [BUG] feedback request uses same keys as confirmation #10126

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[jonyoder]

The reported duplicate (#10126) actually reports the inverse, although it's quite related. This is probably more related to #8743.

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[github-actions]

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.