Uh oh!
There was an error while loading. Please reload this page.
[Feature]: Queue follow-up messages while the agent is running #6885
RoshanMhatre
started this conversation in
Ideas
Replies: 1 comment
when when this? it's been months already 😢 |
0 replies
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/web
Problem or use case
While the agent is running a turn, the composer is effectively locked: Enter-to-send is disabled and the send button is replaced by stop, so the only options are to interrupt or to sit and wait for the run to settle. If I notice a follow-up mid-turn ("also rename the store", "then run the tests"), I have to either kill useful in-flight work or hold the thought in my head and hope I remember it when the run finishes. Related: #4550 and #231 both touch this, but bundle it with a to-do list / steer modes / settings; this issue proposes only the minimal queue.
Proposed solution
Let the composer accept messages during an active run and queue them; drain the queue in order when the run settles.
Cursor's queued-messages stack and Codex's queue-on-enter are the reference UX here — both are small, quiet UIs attached to the composer, not a new surface.
Why this matters
This is the standard workflow in comparable agent frontends (Cursor, Codex, Claude Code): users think ahead while the agent works, especially on long turns, and queueing means stepping away doesn't stall the thread. It also removes the most common reason for interrupting a healthy run.
Smallest useful scope
Queue-on-Enter while a run is active + a visible queued stack above the composer with remove, + auto-dispatch of the queue head when the run settles, persisted server-side. Reordering, inline edit, send-now/interrupt, and any steer mode can all come later.
Alternatives considered
Risks or tradeoffs
Examples or references
Contribution
All reactions