While a run is active, further input is queued locally (edit, delete, send-now). Completed or failed runs drain the queue in order.
HTTP 409 enqueues instead of only showing a failure toast.
The right rail gains a Files tab that reuses the artifacts panel.
Test plan
tsc and vitest 42, including outbox helpers
Dev make test
Click through: start a long reply, queue a second message, confirm it sends after the run ends
## Summary
- While a run is active, further input is queued locally (edit, delete, send-now). Completed or failed runs drain the queue in order.
- HTTP 409 enqueues instead of only showing a failure toast.
- The right rail gains a Files tab that reuses the artifacts panel.
## Test plan
- [x] tsc and vitest 42, including outbox helpers
- [x] Dev make test
- [ ] Click through: start a long reply, queue a second message, confirm it sends after the run ends
Why: a busy conversation rejected further input, and the file list lived
only behind the workspace overlay.
Evidence: npx tsc --noEmit and vitest 42 tests, including outbox
append/edit/promote. The queue uses Collapsible and design tokens.
The files tab reuses ArtifactsPanel.
Impact: while a run is active, Enter queues the draft (edit, delete, or
send-now). Finished and failed runs drain the queue. HTTP 409 also
enqueues instead of only toasting. Backend serialization is unchanged.
Refs: task feature/input-queue
Co-authored-by: Cursor <cursoragent@cursor.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Test plan