feat: queued follow-up messages in composer #58

New issue

Closed

opened 2026-05-28 11:43:21 +02:00 by dries · 1 comment

dries commented

2026-05-28 11:43:21 +02:00

Owner

From spec/multi-agent-support/agent-feature-survey.md — finding #6.

What it is

While the agent is working on the current turn, you can type the next prompt; it queues and sends automatically when the current turn completes.

Seen in

Windsurf/Cascade ("Queued Messages").

ocman angle

Today the ocman prompt input is bound 1:1 with the agent state. We could let users queue N follow-ups in a visible list under the input; ocman watches for finish on the SSE stream and dispatches the next one via the HTTP proxy. Reordering and deletion are free since the queue lives in ocman state.

Effort

S. Pure UI + a small queue manager in the frontend.

From [spec/multi-agent-support/agent-feature-survey.md](../src/branch/main/spec/multi-agent-support/agent-feature-survey.md) — finding #6. ## What it is While the agent is working on the current turn, you can type the next prompt; it queues and sends automatically when the current turn completes. ## Seen in Windsurf/Cascade ("Queued Messages"). ## ocman angle Today the ocman prompt input is bound 1:1 with the agent state. We could let users queue N follow-ups in a visible list under the input; ocman watches for `finish` on the SSE stream and dispatches the next one via the HTTP proxy. Reordering and deletion are free since the queue lives in ocman state. ## Effort S. Pure UI + a small queue manager in the frontend.