Editing Messages

The Message Queue

While the agent is running, you can compose and queue additional messages. They will be delivered to the agent one at a time, in the order they were queued, after the agent finishes its current turn. This lets you:

• Line up several follow-up instructions without waiting for each one to complete.
• Change your mind and edit or remove a queued message before it is acted on.
• Send a message immediately, skipping the queue, if you need the agent to act on it right away.

Queued messages are persisted to disk (queued_messages.json inside the task directory), so they survive a reload.

Built-in slash commands keep their command behavior instead of being sent to the model as normal text. If you submit /compact while the agent is still running, Kodik compacts the conversation immediately and fences off late results from the old turn. /newtask also stays a command rather than becoming queued chat text.

If Kodik is waiting for tool approval and you type a replacement message, Kodik starts that replacement turn immediately. Older queued drafts stay in the queue for you to edit, remove, or send manually, and do not silently run after the replacement turn finishes.

Editing a Sent Message (Checkpoint Restore)

If the agent has already acted on a message you want to change, use the checkpoint restore flow instead. This rewinds both the conversation history and the file state to the point just before that message was processed, then lets you re-send a revised version.

If you edit while the previous response is still streaming, Kodik stops that response as part of the restore and sends the revised message immediately; it is not left in the message queue.

See Checkpoints for details.