Hermes resume session support for Claude Code and Codex is here: a single command — hermes --resume, pointed at claude or codex — picks up your exact session from either tool inside Hermes Agent, context intact. The share came from community educator tonbi (the tonbistudio account on X) on 5 September 2026, complete with a short walkthrough video demonstrating it. Straight up front on sourcing: this is community-shared news rather than an official changelog entry, and the post doesn't say which Hermes version introduced it. But if it works the way the walkthrough shows, it's the most quietly important agent workflow upgrade I've seen in months.
📺 Watch: Hermes + OpenClaw + Claude is INSANE!
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
I run Hermes alongside Claude Code and Codex daily, so here's what was shared, why it matters, the workflows it unlocks — and the open questions to verify before you build anything critical on top of it.
What resuming a session actually means
Every agent tool keeps a session: the running conversation in which the agent has read your repo, understood your task and built up an expensive picture of what's going on. Until now, that session lived and died inside the tool that created it.
The reception on tonbi's thread nailed that pain. One developer said they used to restart cold and re-explain the whole repo every time they moved tools, and that resuming the Claude session with its context intact is what actually saves time. Another community post called the ability to pick up an exact Claude Code or Codex session later "the feature every agent workflow is missing". That matches my experience: the context is the asset, and losing it at every tool boundary is the hidden tax.
As shared, this isn't an export or a summary of chat history — it's the same session, continued inside Hermes.
How the Hermes resume session command works (as shared)
The whole thing, exactly as tonbi posted it, is one command with a pointer at the tool you're coming from. Run hermes --resume @claude to pick up your Claude Code session, or hermes --resume @codex to pick up your Codex session, and Hermes Agent carries on from where that tool left off. The short walkthrough video tonbi published demonstrates the flow.
That's deliberately where my description stops: the post shared the command and showed it working; it didn't share flags, options or setup steps, and I won't invent any. It also doesn't state which Hermes version introduced the feature, so check the official Hermes docs or the help output on your own install for the exact usage before you lean on it.
Want the workflows, not just the news? Inside AI Profit Boardroom I share the exact Hermes, Claude Code and Codex setups I run every day — join AI Profit Boardroom and steal my cross-tool session workflows. And if you'd like a personal plan first, book a free SEO strategy session and I'll map this to your business.
📺 Watch: Hermes3D Is INSANE: AI Agents Now Have a 3D Office
Why this matters: the bridge between tools keeps growing
Session resume is the next step in an interop trend that has been building all year. First came shared instruction files: the big harnesses now read each other's AGENTS.md and CLAUDE.md files, so one set of project instructions steers whichever agent you open, and when DeepSeek's harness launched reading Claude's formats too, it was obvious that cross-tool compatibility had become the expectation rather than the exception.
Sessions are the layer above instructions. Instructions tell an agent how to behave; a session is the actual work in flight. Hermes has been pushing at persistence internally for a while — its memory system already carries context across its own sessions — and resume, as shared, extends that idea across tool boundaries. Your context stops being locked inside one vendor's tool.
That last sentence is my Agent OS thesis becoming real. I've been saying it for months: tools churn, owned workflows compound. The whole reason I tell people to build their own system around these agents — rather than marrying one tool — is so the work survives when the tooling shifts. Session portability is that argument turned into a feature. The moment a session can leave the tool it started in, the tool becomes a component, and your workflow becomes the asset.
The practical workflows this unlocks
Staying grounded in how the community framed it on the thread, three workflows jump out:
- Start in Codex, end in Hermes. One post summed the whole feature up in those exact words: "start in Codex and end in Hermes". Begin a task in whichever tool suits the first phase, then resume the session in Hermes to finish it.
- Hand a Claude Code debugging session to your Hermes roster. If you've spent an hour in Claude Code narrowing down a bug, that hour of built-up context is the valuable part. Resuming the session inside Hermes means your roster inherits the investigation instead of restarting it.
- Keep long-running work moving when you switch tools. As another community post put it, switching tools is far less painful when the context comes with you. Long tasks no longer need to end where one tool's session ends.
📺 Watch: Hermes Bot Mode DESTROYS Grok Bot? (FREE!)
The open questions before you rely on it
The thread wasn't all applause — the sharpest replies asked exactly the right questions. All of these remain open, not answered: verify each on your own setup before session resume becomes part of anything critical.
- Does resume restore tool state, or just the conversation? A session is more than a transcript. Whether resume carries tool state across, or just the conversation context, is — per the thread — unanswered.
- Do the two tools need to be on the same machine? Also raised on the thread and not settled by the post. If you split work between a laptop and a server, test this one before you plan around it.
- One task now leaves a trail in three transcript formats. This was the sharpest observation in the replies: adding up what a single task actually cost now means parsing three different logs. If you track agent spend seriously, that's real bookkeeping overhead.
- Check what access travels with the session. A sensible caution from the thread: when an agent carries work across sessions, it's worth checking what access it carries with it. Know what a resumed session can touch before you resume it.
Where this fits with the existing pairings
If you've followed my coverage, you'll know these tools already work together by design. My Hermes Agent and Claude Code page covers their division-of-labour pairing — each tool doing what it's best at — and Hermes Agent and Codex pair up the same way. For the plumbing, I've got step-by-step guides to connect Hermes Agent to Claude Code and to connect Codex to Hermes.
Think of those pages as the setup guides and this page as the bridge news: resume, as shared, is what turns two tools running side by side into one continuous workflow. Once I've had proper hands-on time with it, it'll go through the same testing process as everything else on Goldie Bench — until then, treat this as reported rather than benchmarked.
The v0.21 timing context
Hermes v0.21 — the Pantheon release on 31 August — made the roster persistent, and less than a week later the community is sharing session resume across tools. I can't tell you which release introduced resume — the post doesn't say — but the direction is consistent: persistence inside Hermes first, then across tool boundaries. Whichever version you're on, update Hermes and check the docs rather than assuming you have it.
What's confirmed and what's open
| What | As shared | Status |
|---|---|---|
| The command | hermes --resume with @claude or @codex | Confirmed by the share |
| Picks up the exact session, context intact | Demonstrated in the walkthrough video | Confirmed by the share |
| Works from both Claude Code and Codex | Both pointers shared | Confirmed by the share |
| Restores tool state as well as conversation | Raised on the thread | Open question |
| Works across separate machines | Raised on the thread | Open question |
| Single view of cost across three transcript formats | Raised on the thread | Open question |
| Hermes version that introduced it | Not stated in the post | Check the official docs |
Hermes resume session FAQ
What is Hermes resume session?
It's community-shared support for picking up your exact Claude Code or Codex session inside Hermes Agent with a single command — hermes --resume, pointed at claude or codex — context intact. It was shared by community educator tonbi on X on 5 September 2026, with a walkthrough video.
Does it work with both Claude Code and Codex?
Per the share, yes: hermes --resume @claude resumes a Claude Code session and hermes --resume @codex resumes a Codex session inside Hermes.
Does it carry tool state or just the conversation?
That's an open question straight from the thread, and I haven't seen it answered. Until it is, assume the conversation context comes across and verify anything beyond that yourself.
Which Hermes version do I need?
The post doesn't say. Update Hermes, then check the official docs or your install's help output — that's the honest answer until it's formally documented.
Is this an official Hermes feature?
It's community-shared: tonbi posted the command with a walkthrough video demonstrating it. Confirm it through official Hermes channels before you make it part of a production workflow.
My verdict
The community post that called this "the feature every agent workflow is missing" wasn't exaggerating. Instruction files taught these tools to read the same brief; session resume, as shared, lets them continue the same work — the difference between owning a pile of tools and owning a workflow. Verify the open questions first, especially tool state and access. But the direction is unmistakable: your context is becoming portable, and hermes resume session support is one more sign the owned-workflow era is arriving.
Ready to build a workflow that survives tool churn? Join AI Profit Boardroom and get my complete cross-tool agent playbook — the setups, sessions and systems behind everything I publish here. Prefer a personal roadmap? Book a free SEO strategy session and we'll map your fastest route together.
