Skip to content

feat(composer): queue follow-up messages while task is running (#608) - #641

Open
cagdasyurekli wants to merge 2 commits into
andrewyng:mainfrom
cagdasyurekli:feat/issue-608-queue-messages
Open

cagdasyurekli wants to merge 2 commits into
andrewyng:mainfrom
cagdasyurekli:feat/issue-608-queue-messages

Conversation

@cagdasyurekli

@cagdasyurekli cagdasyurekli commented Sep 6, 2026

Copy link
Copy Markdown

Closes #608

Changes

Allow follow-up messages to queue while a turn is running. Keep queues scoped to their originating session, display removable items, and send one item at a time after that session reports ready and idle. Optional request IDs are echoed by the server on acceptance or rejection, so attachments and skill messages are acknowledged correctly. Keep a rejected or disconnected pending item visible with an error; remove accepted items only on turn_start. An awaiting acknowledgement does not claim a running agent turn.

Verification

  • Full Python suite: pytest tests -q — 1,956 passed, 1 skipped (macOS, Python 3.14).
  • GUI: 181 unit tests passed; tsc --noEmit passed.
  • Playwright: 224 tests passed in the full run; after correcting the attachment text locator, all 7 queue/composer regressions passed, including attachment acknowledgement, rejection recovery and session isolation.

cagdasyurekli and others added 2 commits September 6, 2026 03:39
…wyng#608)

- Define QueuedMessage in types.ts
- Allow composing and queueing follow-ups via button or Enter while running
- Display queued messages strip above composer with count and remove action
- Automatically drain queue and send next message sequentially when task finishes
- Add i18n translations in English and Chinese
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Queue messages so follow-ups can be composed while a task is running

1 participant