Skip to content

QUEUE + manual approval causes unintended auto-rejections & Enter key UX issue #6996

@boukeversteegh

Description

@boukeversteegh

Description

When using the new QUEUE feature with manual approval enabled, a follow-up message placed in the queue causes the next approval gate to be auto-handled. The run immediately continues and the LLM behaves as if the pending request was rejected, without user confirmation.
This does not happen when auto-approve is enabled.

Steps to Reproduce

  1. Disable auto-approve.
  2. Give the agent a task that will eventually require approval.
  3. Queue a message, e.g., "and after that please build xyz".
  4. Wait until the agent reaches a step that requires approval.
  5. Observe: it immediately continues, and the LLM output indicates the request was treated as rejected.

Expected Behavior

  • When manual approval is enabled, reaching an approval step should pause and wait for explicit user action, regardless of queued messages.
  • In general, sending a free-form text message and pressing Enter should not implicitly reject the request.
    Instead, the UI should guide the user to explicitly approve or reject.
    This allows for workflows like “Yes, and …” where the user can append follow-up instructions without wasting tokens on re-summarization or prematurely triggering a task_complete action.

Actual Behavior

  • The run continues automatically and the model assumes the approval request was rejected.
  • In non-QUEUE scenarios, pressing Enter with a text reply still counts as a rejection.

Impact

  • Breaks manual-approval workflows; QUEUE + manual approval are effectively incompatible.
  • Discourages quick inline approval with appended instructions.

Environment

  • Roo Code version: 3.25.11
  • Platform: Windows
  • Manual approval: Enabled
  • Auto-approve: Disabled
  • QUEUE: Enabled

Possible Workaround

Enable auto-approve (issue does not reproduce).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue - Needs ScopingValid, but needs effort estimate or design input before work can start.bugSomething isn't working

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions