Stash and Restore Draft Prompts in the Hermes CLI

A long prompt does not need to block a quick question. In the Hermes CLI, Ctrl+S parks the current composer draft and clears the input so you can work on something else. Pressing Ctrl+S on an empty composer restores the most recent draft.

Use the draft stack

Repeated stashes form a stack instead of overwriting earlier drafts. When more than one draft exists, the browse panel lets you use arrow keys to choose an entry, Enter to restore it, D to discard it, and Escape or Ctrl+S to close the panel.

Multiline text and attached images travel with the draft. The stash is session-memory-only: it is not written to disk and should not be treated as durable storage.

Working checklist

Stash before replacing a substantial draft with a quick prompt.
Confirm attachments reappear with the restored draft.
Remove obsolete drafts deliberately from the browse panel.
Copy critical long-form work to a durable file before ending the session.
Avoid parking secrets or private material longer than necessary.
Restore and review the full draft before sending.

Common pitfalls

Expecting drafts after a restart. The stack exists only in the active session memory.
Pressing Ctrl+S with an empty composer unintentionally. That restores or opens the draft browser.
Sending a restored draft without re-reading it. Context may have changed while it was parked.
Treating stash as version control. It is a convenience buffer, not a revision history.

Verification

Create two harmless multiline drafts, attach a public test image to one, and stash both. Browse the stack, restore each in turn, and confirm text, line breaks, and attachment state. End only a disposable session to verify that drafts are not durable.

Official reference: Hermes CLI guide.