Editable follow-up queues for Agent sessions
You can now line up the next instructions while an Agent session is still working. Sending during an active turn adds the message to a visible first-in, first-out queue instead of interrupting the agent or making you wait at the composer. Each waiting row shows its place in line, keeps its task context and attachments, and can be edited or removed until dispatch begins. The Stop control remains available beside the new queue action, so preparing later work never takes away control of the turn already running.
Pekan owns the queue per session and saves it with the session record. Waiting messages survive panel navigation and an app restart, and they are submitted one at a time only after the previous turn finishes successfully. Repeated completion events cannot send the same item twice. If a connection fails, a restart catches a message during dispatch, or a persistent provider session needs to be resumed, the affected item stays visible with a clear failure state instead of disappearing or moving later messages ahead of it.
Failed items can be retried or removed. Editing keeps the original queue position, and deleting an item closes the gap without disturbing the order around it. A message locks as soon as dispatch starts, then moves into the conversation transcript when Pekan hands it to the provider. Cancellation and other non-successful stop reasons leave later messages waiting for an explicit user action, preventing unexpected work from starting after a session was deliberately stopped.
Highlights
- Compose and queue follow-up instructions while an Agent turn is active.
- Edit or remove waiting messages without changing their FIFO position.
- Queues persist across navigation and restart, with duplicate-dispatch protection.
- Failed messages stay visible and offer retry or removal controls.
- Cancellation never launches the next queued instruction automatically.