The Hermes Agent /btw command is for the question you’d whisper to a colleague without stopping the meeting: /btw <question> gets you a quick answer about the current conversation without interrupting the work in progress. Under the hood it’s cleverer than it looks — here’s the documented behaviour and where it fits.
Short answer
/btw <question>poses a quick auxiliary question about the current conversation — without interrupting ongoing work.- Mechanism, per the official slash-commands reference: a one-shot auxiliary LLM call answers from a read-only snapshot of the transcript.
- The live session’s history and prompt cache are untouched — /btw leaves no fingerprints.
- Works in the CLI and the messaging gateway.
What the Hermes Agent /btw command does
The documented mechanism is the whole story: when you fire /btw, a one-shot auxiliary LLM call reads a read-only snapshot of your transcript and answers your question from it. Nothing enters the live session’s history; the prompt cache stays warm and untouched. Your main line of work literally cannot tell it happened.
That makes /btw the zero-cost curiosity valve. “What did we decide about the pricing section?” “How many files has this touched so far?” “Summarise where we’re up to” — the questions you’d otherwise either interrupt the agent to ask, or scroll ten minutes to answer yourself.
Hermes Agent /btw vs the commands it gets confused with
| Command | What it touches | Use when |
|---|---|---|
/btw <question> | Nothing — read-only snapshot | You need an answer about this conversation |
/bg <prompt> | A separate background session | You need new work done in parallel |
/busy steer | The live task, after next tool call | You need to redirect work in progress |
The mix-up is common enough that users publicly confessed to using /bg for years of side questions. The distinction that sticks: btw asks, bg does. If your “question” starts generating new artefacts, it was a /bg all along.
🔥 Want this set up without the guesswork? A frictionless agent workflow where /btw-style checks are habit is exactly the kind of thing we set up together inside the AI Profit Boardroom — 3,700+ members, four live calls a week, daily tutorials, done-for-you templates and a 30-day roadmap. Prefer 1-on-1 help? Book a free SEO strategy session and we’ll map it out for your business.
Where /btw quietly changes your workflow
The prompt-cache detail is the underrated part. Long agent sessions build expensive warm context; anything that injects turns into the live history perturbs it. Because /btw runs against a snapshot, you can be freely curious — status checks, sanity checks, “wait, why did we…” moments — at zero cost to the session’s state or economics. Curiosity stops being something you ration.
From the messaging gateway it’s even better: a /btw from your phone reads the state of a long-running session without touching it — a status report that can’t accidentally become an instruction. For the acting-on-a-busy-agent cases, that’s /busy’s job instead.
The bottom line on Hermes Agent /btw
Hermes Agent /btw is a small command with a precise contract: one-shot answer, read-only snapshot, zero disturbance to history or cache. Learn the ask vs do line against /bg and it becomes the command you use twenty times a day without thinking — which is the highest compliment slash commands get.
Twenty tiny questions a day
The way /btw earns its keep is frequency. Through a normal working session mine looks like: “/btw what did we decide about the header copy?” before repeating a settled argument; “/btw how many pages have we touched so far?” before a status ping to a client; “/btw summarise the open questions” before a break so re-entry is instant; “/btw did we already try the cache-first approach?” before suggesting it a second time.
None of those deserved an interruption; all of them used to cause one — or a long scroll. Because the snapshot answer costs the session nothing, the right amount of /btw is “whenever you’re mildly curious”, which is a genuinely different way of working with a long-running agent: the transcript becomes something you query, not something you re-read.
A last nuance worth knowing: because /btw reads a snapshot, its answer reflects the conversation as it stood the moment you asked — not whatever the agent produced two seconds later. In fast-moving sessions that’s occasionally visible, and it’s the correct trade: a perfectly current answer would require touching the live session, which is precisely what /btw promises never to do. If you need an answer that accounts for in-flight work, wait for the turn to land, then ask — the snapshot will have caught up.
FAQ: hermes agent /btw
What does /btw do in Hermes Agent?
It answers a quick auxiliary question about the current conversation via a one-shot LLM call against a read-only transcript snapshot — without interrupting ongoing work, per the docs.
Does /btw affect my session or prompt cache?
No — the live session’s history and prompt cache are untouched; that’s the documented design.
When should I use /btw instead of /bg?
/btw for questions about this conversation; /bg for new work in a separate background session. Ask vs do.
Can /btw take actions or use tools?
It’s a one-shot auxiliary answer from a snapshot — for work that acts, use /bg or the main session.
Where does /btw work?
CLI and the messaging gateway.
Why not just ask in the main session?
A normal turn enters history, interrupts in-progress work and touches the cache — /btw does none of the three.
Next step: if you want an agent setup you can question without breaking working for you this week, join the AI Profit Boardroom for the full walkthroughs and live help — or book a free SEO strategy session and I’ll point you at the fastest path for your situation.
About Julian Goldie: SEO agency owner with 10+ years in SEO, 394K+ subscribers on YouTube, a 100% job-success score on Upwork, 75K+ members across his communities, and author of a best-selling SEO book. He runs the AI Profit Boardroom community and offers a free SEO strategy session.
Related reading
- Hermes Agent /bg: Background Tasks Explained
- Hermes Agent /busy: Queue, Steer Or Interrupt
- Hermes Resume Session: Continue Claude Code & Codex
Last updated September 2026. This is the living guide to hermes agent /btw — it gets updated as the tools change.