When Hermes Agent is busy, you can directly send another sentence, and by default, "Interrupt + New Message Takeover" will be triggered. The role of /stop is to only interrupt and not accompany new follow-up tasks. This distinction is very important in long missions.
When to send a direct message
It is suitable for you to specify the need to change, such as "pause, change to only look at the staging environment". Hermes will terminate the current run and treat your new content as your next input.
When to use /stop
It is suitable for you who simply want to stop, such as when the command is obviously off, should not continue, or if you want to observe the current state before deciding on the next step. The official documentation makes it clear: /stop is interrupts without queuing a follow-up message.
If you often operate a server in remote chat, this distinction is very valuable: the former is "change the topic", the latter is "emergency stop".
In a word: /stop is only responsible for braking, and the direct message is to change the steering wheel immediately after braking.
Why this is especially important in remote scenarios
When you operate Hermes in Telegram or Slack, you may not immediately see the terminal status. /stop first helps you stop the action, and then decides on the next sentence; Direct messaging will spell the new content into a follow-up task by default. This difference is especially critical for bad commands, long builds, and misoperation troubleshooting.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
