Skipping Agent questions with a prompt

So in the past when communicating with an agent through the IDE tab, I was able to circumvent Agent questions and simultaneously guide the Agent down a different reasoning path. This was usually caused when the Agent’s response and questions suggested that it missed my intent, and it was helpful to redirect its reasoning. So instead of answering the questions I would just respond with a new prompt.

Now, when I do that, the prompt does not reach the agent, and instead it assumes I skipped everything and it accepts the default option A for each question and proceeds - exactly the opposite of what I want. I then have to immediately stop it and ask, again.

This issue ranges from slightly annoying to absolutely harmful. Not sure what it works like this now, but I would love to bring back the old mechanism.

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hey, thanks for the detailed report. This is a known issue we’re already tracking, and I’ve shared your thread with the team. Right now, when you send a new message while there are open questions, it skips those questions first. Because of that, the agent can accept the default options before it reads your message. This isn’t something in your setup.

For now, there are two workarounds:

  • First click Stop, then send your new prompt. The agent will see the skipped questions and your message together in the same turn.
  • Or pick “Other” on the question and type your redirect there. That way your text is sent to the agent as the answer.

I can’t share a timeline yet, but I’ll reply in the thread when there’s an update. Let me know if the workaround doesn’t help.

Small update on this thread: the fix for the case where a new request, with Agent questions still open, skips the questions is included in Cursor 3.23. After that, your message reaches the agent together with the skipped questions, and the agent responds to what you wrote instead of falling back to the default options.

On the current stable version 3.22.x, the fix isn’t in yet. So until you update to 3.23, the same workarounds apply: click Stop first, then send a new request, or pick Other and type your redirect there.

Once you’re on 3.23, try again and let me know if the issue is still happening.