Queueing an 'ask-mode' question breaks running implementation

Support Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

When the agent is busy implementing a large plan, editting and creating files, I want to already queue new messages for when it finishes. But if the queued message is of type ‘Ask’ instead of ‘Agent’, the running agents patch-tool instantly breaks/blocks, causing the running task to break.

Steps to Reproduce

  1. Have agent edit a number of files
  2. While its busy, type a new message, set type to ‘Ask’, sent. Do this before it finishes editting files, so it gets queued.
  3. Current task breaks as patch-tool blocks as soon as ask-message is queued.

Expected Behavior

Keep running task without instantly blocking patch-tool, delay switch to ask mode (and block the patch-tool) when starting to handle the queued message.

Operating System

MacOS

Version Information

Version: 3.9.8
VS Code Extension API: 1.105.1
Commit: 4aa8ff1b7877ed7bd01bcba308698f71a6735380
Date: 2026-06-25T01:39:30.490Z (1 day ago)
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @David_GM!

Thanks for the feedback. We’ve heard about this before (Chat mode affects actual run) and it’s definitely annoying behavior. We have an open bug report this time, and I’ve attached your report!

Until it’s fixed, keep the queued/follow-up message in Agent mode while the current task is running, and only switch to Ask after the running turn finishes.

7

The key distinction is that queueing should be passive until the current turn finishes.

If switching the next message to Ask changes tool permissions immediately, then the queued message is no longer just queued. It is mutating the running execution state, which is exactly the surprising part.