Sent messages history and messages held by a CLI question
- Desktop app
- All plans
What it does
Two safety nets around the composer of an agent. First, when the agent's CLI is waiting on a question of its own (Claude's multiple-choice questions, a permission prompt), a message you send is no longer typed into that question, where it used to disappear: it stays in the composer and a notice explains why, with a way to send it anyway. Second, a History button lists every message you sent to this agent in the current conversation; one click puts a message back in the composer, text and attached files included, to send it again or amend it.
Where to find it
- The notice appears right above the composer of the agent, only when you press Send while the CLI is waiting on a question: "Not sent: the agent is waiting for an answer to its question."
- History is a button of the composer toolbar, next to Prompt library. Its popover is titled Sent messages.
How to use it
- The agent asked a question and you sent a new message instead: the notice appears and your message stays in the composer.
- Click Skip the question and send: AgentsRoom presses Escape in the agent's terminal (the question is declined, like in the CLI), waits for the prompt to come back, then sends your message with its files. Or click Add to queue to keep the message as a queued card, or answer the question in the terminal or from the question card of the Conversation view: the notice then leaves on its own and your message is still there, one Send away.
- To send a previous message again, click History, search if needed ("Search sent messages…"), and click the message: it goes back into the composer with its files. Messages are numbered and separated, each shown on three lines at most so a long one does not hide the others. Whatever the composer held goes to the queue first, nothing is overwritten.
Typing only an option number (1, 2…) or y / n is still sent straight to the question: that is how you answer it from the composer.
Settings
composerHiddenActions(global, Settings > Composer > Composer toolbar buttons): addhistoryto hide the History button ("Sent messages history"). Shown by default.
Agent tools (MCP)
None.
Providers
All providers. The question detection relies on AgentsRoom's "waiting for input" status of the CLI (a question or a permission prompt shown by the CLI itself), which exists for every provider AgentsRoom tracks. Skip the question and send presses Escape: Claude Code records the question as declined and gives the prompt back; in the other CLIs, Escape cancels the pending request the same way.
Mobile
The phone's messages go through the desktop: while the CLI waits on a question, a message from the phone (or a broadcast, or a scheduled message) is held in the agent's queue, marked "waiting for the agent", and sent on its own as soon as the question is answered. The History button itself is desktop only for now.
Limits
- The history covers the current conversation of the agent:
/clearor a new session starts it empty. It is kept on this computer only. - A message recorded before 2026-09-28 comes back without its
File #Nnumbers: a reference typed in its text may no longer point at its file.
Common questions
- I sent a message while the agent was asking me a question and nothing happened, is it lost? Since 2026-09-28 it is not sent at all: it stays in the composer with a notice. For an older one, open History (or the Conversation view): the message is listed there and one click puts it back in the composer.
- Can I send a new instruction without answering the agent's question? Yes: Skip the question and send.
Related
- Message Queue: where Add to queue puts the held message.
- Conversation View: answer the agent's question from its card.