What happens if I message Hermes while it is still working?
By default, a plain text message sent while Hermes is working corrects the current task rather than starting a new one. Hermes keeps the work it has already completed and reads your message at the next safe point, without killing a running tool. You can change this so new messages wait for the next turn (queue) or are slipped into the run after the next tool call (steer). /stop is the hard stop.
This follows Hermes Agent v0.23.1, commit 3b42157, checked on 17 November 2026. It covers chats through Hermes’s messaging gateway, such as Telegram, Discord or Slack. The classic Hermes terminal chat offers the same three modes; the full-screen terminal interface defaults to queue instead. We reviewed official documentation and source. We did not send messages to a running task on a Vavio computer, or measure how quickly a correction lands.
Which mode is my Hermes using?
Send /busy in the chat. Hermes replies with the current mode and how to change it. The setting is display.busy_input_mode in each Hermes profile’s config.yaml, and the default is interrupt. The first time Hermes acknowledges a message sent while it is busy, it adds a one-time tip about this setting.
| Mode | What a text message does while Hermes is busy | Acknowledgement |
|---|---|---|
interrupt (default) |
Redirects the current turn with your correction | ↪ Redirected current run |
queue |
Waits, then runs as its own turn after the current task finishes | None for plain text; it simply runs next |
steer |
Is delivered into the current run after the next tool call, without a new turn | ⏩ Steered into current run |
Acknowledgements are sent at most once every 30 seconds and can be switched off with display.busy_ack_enabled: false, so a missing reply does not mean your message was lost.
To change it from chat, send /busy queue, /busy steer or /busy interrupt. Hermes saves the choice to the profile’s config. If your setup restricts slash commands to admins, a non-admin may not be able to change it.
What does the default “interrupt” mode actually do?
In the pinned source, the default mode redirects the turn for a plain text message. What that means depends on what Hermes is doing at that moment:
- While the model is writing a response, only that model request is cancelled. Messages already completed in the turn are kept, partial reasoning becomes context, and your text is added as a correction. The same turn then retries with it.
- While a tool is running, the tool is not killed. Your text is delivered when the current tool step returns. A long foreground terminal command, such as a build, is asked to move to the background so your message can be read sooner. Hermes does not stop the process.
- Between steps, when neither a model request nor a tool is running, Hermes falls back to a full interrupt (“⚡ Interrupting current task”) and your message runs as the next turn.
- If the agent has not started yet, your message waits and runs as the next turn.
On Telegram, a text sent within about three seconds of a run starting is merged into that run’s pending input rather than redirecting it, so a quick follow-up to your first message is treated as part of it.
Two conditions switch the default mode to queueing for that message: Hermes is running subagents, or it is compressing the conversation context. Interrupting either would abort that work, so Hermes queues your message and says so. Send /stop if you want to cancel everything instead.
Do photos, voice notes and files behave differently?
Yes. In the default mode, a redirect accepts plain text only. A voice note, document or video sent while Hermes is busy can interrupt the current task and then run as the next turn. Unlike a text redirect, an interrupt aborts tool calls in progress: a running foreground terminal command is killed and reported as interrupted. Hermes transcribes a voice note first and uses it as the interrupt message. Photos are usually queued without interrupting, so that a burst of photos arrives together, although some gateway paths treat a photo like other attachments. If you don’t want to risk stopping a long command, send the attachment with /queue or switch to queue mode first.
In steer mode, plain text is steered, and on most gateway paths so are voice notes Hermes can transcribe. Other attachments fall back to the queue.
When should I use queue or steer?
Use queue if your follow-ups are separate requests. Each message gets its own turn in the order received (texts sent within a fraction of a second of each other are merged into one), so “also summarise yesterday’s email” does not change the report Hermes is already writing. A rapid burst of photos is merged into one album turn.
Use steer if you often add guidance to long tool-heavy tasks. For example, “focus on the invoices from October” while Hermes is still searching. The note reaches Hermes after its next tool call and does not open a new turn. If no further tool call happens before the turn ends, your note becomes the next turn instead of being lost. A steer sent while subagents are running also goes to those subagents.
Keep the default if you mostly send corrections. It is the fastest way to change direction without discarding finished work.
You can override the mode for a single message whatever the setting: /queue <message> always waits for the next turn, and /steer <message> always tries to steer, falling back to queueing when there is no run to steer.
What if Hermes is waiting for my approval?
When Hermes is blocked on a dangerous-command approval, a message consisting of one exact approval word is treated as your answer, not a new message. yes, ok, approve or 👍 approves the command. no, deny, cancel or 👎 denies it. Anything longer, such as “no, use the other folder”, is handled as an ordinary busy message. always and session widen the approval as they do with /approve. This only applies while an approval is actually pending. To stop the whole task rather than refuse one command, use /stop. The approvals guide covers what triggers these prompts.
How do I stop everything, or ask without disturbing it?
/stopcancels the active turn and its foreground work. Hermes replies “Stopped. You can continue this session.” It also drops a steer that has not been delivered yet, interrupts background subagents for the conversation and can discard a follow-up that was still waiting to run, so resend anything you still want done./btw <question>asks a side question about the conversation without interrupting it. It is answered from a snapshot of the transcript and leaves the running turn alone./bg <prompt>runs a separate prompt in its own background session.
Stopping a scheduled job’s current run is a different control. See how to stop a running Hermes job without deleting its schedule.
What happens to my message during a restart?
Hermes saves most chat messages in a per-conversation queue. While the gateway is restarting, it may reply “⏳ Hermes is restarting — your message is saved and will be answered when it is back.” On some paths the busy mode decides instead: queue and steer keep the message for after the restart, while the default interrupt mode replies that Hermes is not accepting another turn right now. Check that your message was answered once Hermes is back, and resend it if not. The restart guide covers what happens to a task that was running.
What hosting changes
With Hermes on a remote computer, a long task keeps running while you message it from your phone. That makes the busy-input choice something you meet often. Vavio supplies a managed Hermes computer for $14.99 per month, with model usage billed separately. Hosting keeps the computer and Hermes running. It does not change how Hermes treats a message sent mid-task: choose the mode that fits how you write to it. Review the current hosting offer if that is the service you need.
Sources
- Hermes v0.23.1 redirecting the agent and busy-input mode, checked 17 November 2026
- Busy-message handling in the messaging gateway, checked 17 November 2026
- Redirect, steer and interrupt inside the agent, checked 17 November 2026
- Foreground commands on interrupt or redirect, checked 17 November 2026
- Slash commands (/queue, /steer, /busy, /stop, /btw), checked 17 November 2026
- Vavio hosting offer, checked 17 November 2026
Written by Vavio with AI assistance and checked against pinned official Hermes v0.23.1 documentation and source. This is a source review, not a live chat, cancellation or task-completion trial.