Wondering how to make a Hermes resume session pull in your existing Claude Code or Codex work? There’s now a single command for exactly that: hermes --resume @claude (or @codex) picks up your exact session inside Hermes Agent, context intact — shown off by tonbi of Tonbi’s AI Garage on 5 September 2026. Here’s how it works, the handoff patterns worth using, and what the demo doesn’t confirm yet.
Short answer
- The command:
hermes --resume @claudeorhermes --resume @codex— resumes that tool’s session inside Hermes Agent. - Context comes with you: no cold restart, no re-explaining the repo to a fresh agent.
- Demonstrated by tonbi (@tonbistudio) with a 4½-minute walkthrough, 5 September 2026.
- Not yet confirmed publicly: whether tool state restores (or just conversation), and whether both tools must share a machine.
How the hermes resume session command works
The pitch is one line long: you’ve been deep in a Claude Code or Codex session — repo context loaded, decisions made, half the work done — and instead of finishing there, you run hermes --resume targeting that tool and carry on inside Hermes Agent. The session comes across as context, so the agent you resume into already knows what the last one knew. As one developer put it in the replies, the old way was restarting cold and re-explaining the whole repo — this is the feature that kills that ritual.
Why resume into Hermes specifically? Because of what’s waiting on the other side: the open-source Hermes Agent runs persistently, keeps memory beyond any single session, and brings its own tools. You’re not just moving a chat log — you’re promoting a throwaway coding session into an agent that will still know about it next week. The full demo is in tonbi’s walkthrough on X.
Hermes resume session in practice: the handoff patterns
| You’re working in | Run | Result |
|---|---|---|
| Claude Code | hermes --resume @claude | That session continues inside Hermes Agent |
| Codex | hermes --resume @codex | Same — context carried into Hermes |
Three patterns emerged in the community reaction within hours. The relay: start a task in Codex or Claude Code, finish it in Hermes — “start in codex and end in hermes” was one reply’s whole workflow. The promotion: when a quick coding session turns into a long-running project, resume it into Hermes where persistence and loop workflows live. And the consolidation: whatever tool you experiment in, the work accumulates in one agent. My setup guides for both ends of the bridge: Hermes + Claude Code and Hermes + Codex.
🔥 Want this set up without the guesswork? Wiring a multi-tool agent workflow like the hermes resume session bridge 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.
What’s confirmed — and what isn’t yet
Honesty box: the demo shows session pickup working, but two sharp questions in the thread had no public answer at the time of writing — does --resume restore tool state, or only the conversation context? And do the tools need to be on the same machine? Until those are confirmed, test with a throwaway session before trusting it with real work. The demo also only shows resuming INTO Hermes — no reverse direction is claimed.
One more practical wrinkle a commenter flagged: a task that hops harnesses now leaves transcripts in multiple formats, so if you track token spend per project, your accounting just got a third file format to parse. Minor, but real for anyone billing agent time.
The bottom line on hermes resume session
The hermes resume session bridge is the interoperability piece agent workflows have been missing: one command, and your Claude Code or Codex context lands inside a persistent agent instead of dying with the terminal tab. Use the relay and promotion patterns, keep the honesty-box caveats in mind until they’re answered, and let the session you’ve already invested in keep earning.
FAQ: hermes resume session
What is the hermes resume session command?
hermes --resume @claude or hermes --resume @codex — it picks up that tool’s exact session inside Hermes Agent, context intact.
Does it work with both Claude Code and Codex?
Yes — the demo shows one flag per source tool, @claude and @codex.
Does it restore tool state or just the conversation?
Unconfirmed — that exact question was asked in the announcement thread and hadn’t been answered publicly at the time of writing.
Do Hermes and Claude Code need to be on the same machine?
Also unconfirmed — the community asked and no answer was posted. Assume same-machine until shown otherwise.
Can I resume a Hermes session back into Claude Code?
The demo only shows resuming into Hermes. No reverse direction has been demonstrated.
Where did this come from?
Demonstrated by tonbi (@tonbistudio) of Tonbi’s AI Garage on X, 5 September 2026, with a 4½-minute walkthrough video.
Next step: if you want a session-portable agent workflow that compounds 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 Claude Code Setup Is Actually Wild
- Hermes Agent + Codex: Setup And When To Use It
- Hermes /loop: Recurring Tasks Inside Your Session
Last updated September 2026. This is the living guide to hermes resume session — it gets updated as the tools change.