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 recent messages 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

  1. The agent asked a question and you sent a new message instead: the notice appears and your message stays in the composer.

  2. 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.

  3. 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.

  4. To free local storage, use Clear all sent-message history in the History popover. This clears the sent-message cache for all agents on this computer, not CLI conversations, draft messages or attached files. A storage error also shows a persistent warning with the same control, even if an agent has not opened.

Suggested reply of the CLI (since 2026-10-27): when Claude Code writes a grey suggestion of your next message in its own input box, an empty composer shows it as its placeholder, with a Use suggestion chip (Tab) on its own line just above the field, below any banner such as Adaptive Model. Press Tab in the empty composer, or click the chip, to put the suggestion in the composer. Nothing is sent: read, edit, then send. With a draft in the composer, or no suggestion on screen, Tab keeps its usual behavior. Nothing is offered while the agent is working.

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): add history to 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.

The suggested reply is Claude Code only: the other CLIs show no suggestion in their input box, so nothing is offered for them.

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. The suggested reply works on the phone too: same placeholder, same Use suggestion chip, and the Tab key of the rail puts the suggestion in the input box when it is empty (not in Direct mode, where Tab stays a terminal key).

Limits

  • The history covers the current conversation of the agent: /clear or a new session starts it empty. It is kept on this computer only.
  • Up to 500 messages per agent remain available while the app is open. The saved history shares a 1 MiB budget across agents: recent complete messages are kept, with fewer saved when local storage is full. The saved cache keeps at most 256 KiB per session, 200 sessions and 30 days. Older or oversized messages may disappear from this history after restarting the app; messages are never shortened. A full history cache never blocks an agent from starting or receiving a message.
  • A message recorded before 2026-09-28 comes back without its File #N numbers: 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.
  • A storage error leaves the composer or new consoles stuck. The oversized cache is reduced automatically at startup. If storage is still unavailable, sends and launches continue; use the warning’s Clear all sent-message history control to free space.
  • Can I send a new instruction without answering the agent's question? Yes: Skip the question and send.
  • How do I accept Claude Code's grey suggestion without clicking into the terminal? With the composer empty, press Tab or click Use suggestion: the suggestion goes into the composer, ready to edit and send.
  • What does Escape do in the composer? The same as in the CLI: it is sent to the agent, which interrupts its current turn so you can edit and resend. Menus open in the composer (mentions, prompt suggestions, find) close first. Before 2026-10-19 Escape in the composer closed the project.
  • Can I use a CLI chord like Ctrl+X Ctrl+S from the composer? Yes, since 2026-10-26: Ctrl+X, then the next Ctrl key (Ctrl+S, Ctrl+E...) typed within about a second and a half, are sent to the agent as if typed in its terminal. In Claude Code, Ctrl+X Ctrl+S moves a queued message to the front. With text selected in the composer, Ctrl+X stays Cut. Other Ctrl shortcuts keep their app and text editing meaning; to send any other key, click into the terminal and type there. On the phone, arm Ctrl in the key rail, then the letter.