Repository navigation
Open
Description
Edit, delete, or choose how a message waiting on a busy chat is delivered: steer, follow-up, or interrupt now.
Done
- Queued messages are visible above the composer for everyone in the chat, live and after reconnect (Restore queued-message visibility above the composer #193,
apps/app/src/message-queue.tsx,packages/channel/src/queue.ts), with authors named as the timeline names them (fix(app): name queued messages' authors as the timeline does #278). Verified in the two-person study ([Meta] Dogfood as a team and ship the Universe story #218, scenario 10). - Every
askto a busy chat is already a steer:packages/channel/src/channel.tssubmits withwhenBusy: "steer", so pi places it after the current tool round. Another channel's queued handoff also interrupts the chat's shell commands (feat(channel): stop a chat's shell commands for another channel's invoked message #400).
Remaining
- Delete a queued message: its author can withdraw it. pi already has per-submission withdrawal (
Submissions.abort(id)); the channel protocol has no op for it. - Edit a queued message: withdraw and resubmit in place, keeping its queue position if pi allows, otherwise say it moves to the end.
- Choose steer (after the current tool round) or follow-up (after the run ends) per message; pi supports
whenBusy: "followUp", the app has no control for it. - Interrupt now: deliver a queued message right away instead of waiting for the current tool round. In-flight tools get aborted and pi reports them to the model as interrupted, then the run continues with the message. Today a person can only queue (as a steer) or Stop. Stop ends the run and sends queued messages back to their authors' drafts (fix: return queued messages Stop withdraws to their authors as drafts #433), so they have to resend by hand. Handoffs from other channels already interrupt shell commands (feat(channel): stop a chat's shell commands for another channel's invoked message #400,
packages/channel/src/handoffs.ts); a person's interrupt should also cover other long tools, and say which ones were cut short (Show when a run was stopped or interrupted, and tell the agent #442). - What Stop does to the queue was decided in Stop silently drops queued messages #279 (fixed in fix: return queued messages Stop withdraws to their authors as drafts #433).
Dogfooding core/QOL: #5. Also tracked in #6 for old-Ace feature parity. Migrated from TODO.md — Port from old Ace.
Metadata
Metadata
Assignees
Labels
No labels
Activity
iamnbutler commentedon Oct 7, 2026
Restoring queued-message visibility first: pending messages currently disappear from the composer until pi places them in the transcript. This work will project pi’s existing durable queue into the chat watch and show it above the composer, including after reconnect. Edit/delete/explicit steering controls remain follow-up scope here.
iamnbutler commentedon Oct 7, 2026
Queue visibility is implemented in an isolated lane. Type checks and lint pass. A real OpenAI gpt-6-astra/source-worker smoke check verified immediate live queue updates, passive Chat messages, reconnect replay, chat isolation, transfer into the transcript, Stop withdrawal, and legacy watchers receiving no new events. Native UI verification and the PR are next. Separately filed #192 for an existing OpenAI tool-schema rejection encountered with gpt-4.1-mini.
iamnbutler commentedon Oct 7, 2026
Opened #193 to restore queue visibility. Verified signed native Ace-dev at 1100×760 and 640×600 with two real queued messages (including an image), plus the real-runtime queue lifecycle checks described above. This PR deliberately does not close #24: editing, deleting, and explicit steering controls still need follow-up.
[-]Edit, delete, and steer queued messages[/-][+]Edit and delete queued messages, and choose steer or follow-up[/+]iamnbutler commentedon Oct 15, 2026
Rewrote the body to current state: queue visibility shipped in #193 (and #278), and busy
asks already steer. What's left is per-message delete, edit, and a steer/follow-up choice; Stop's effect on the queue is split out to #279.[-]Edit and delete queued messages, and choose steer or follow-up[/-][+]Edit and delete queued messages, and choose steer, follow-up, or interrupt[/+]iamnbutler commentedon Oct 19, 2026
Dogfooding (#5): a person can queue a message for a busy chat but can't choose to interrupt the run with it. Added Interrupt now to Remaining. Stop then resend is the only workaround today.