Agent does not auto-resume when replying to an Agent View question from Editor View

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When the agent asks me a question in Agent View, I switch/reply from Editor View. The reply is submitted and appears in the conversation, but the agent does not automatically resume the run.

The agent stays idle/hanging until I send another message like “continue”. After that, it continues normally.

Why I need to work cross views is because the bug of the banner of reach usage limit, mentioned below.

Steps to Reproduce

  1. Start a task in Agent View .
  2. Let the agent ask a clarification question.
  3. Switch to Editor View.
  4. Reply to the question from Editor View.
  5. Observe that the agent does not auto-resume.
  6. Send “continue”.
  7. The agent resumes.

Expected Behavior

After I answer the agent’s question from Editor View, the agent should automatically resume the current run, the same as if I answered directly in Agent View.

Operating System

Windows 10/11

Version Information

Version: 3.3.30 (system setup)
VSCode Version: 1.105.1
Commit: 3dc559280adc5f931ade8e25c7b85393842acf30
Date: 2026-05-09T18:28:42.332Z
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.22631

For AI issues: which model did you use?

auto

For AI issues: add Request ID with privacy disabled

84353a50-46e8-49f4-a3f0-8d74fcf465d3

Additional Information

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report. Having the steps, the Request ID, and the overlay bug context makes this super easy to work with.

The cross-view case with ask_question is a known class of issues. The answer from another view doesn’t get delivered to the agent, so it stays locked on a pending question. I’ll pass this to the engineers so they can check if the latest fix covers your exact case Editor View → Agent View. I can’t share an ETA yet.

If I get an update, we’ll reply in the thread.