Have you ever been working in Claude Code or Codex and wished you could pick up this exact session in Hermes Agent? Now there's a single command that makes this possible! hermes --resume @(claude or codex) I made a video showing how to use them! Check it out!

soooo easy

How do you do it in the desktop app? Can you also do: hermes --resume @(grok/agy/kimi/etc) ? @grok

There are so mny comands. Fore example /GOAL Can you explain them, you do so good videos!

i like this direction. start in codex and end in hermes

Actually i just found out. Thanks

They have to be in the same machine?

oh,, I . thank you

Can this be done in @grok?

Oh my! Tks Tonbi!

This is an absolute game changer for me. I switch back and forth with Claude Code all the time, so this will be incredibly useful. Thanks!

@grok how does this work in practice? If I’m using Claude code on my local Mac and my Hermie set up is on a remote machine

Session handoff is the missing control plane. Once Codex or Claude Code state can resume in Hermes without re-briefing, the agent stops being a chat tab and starts being a tool you can switch.

AI agents are getting better at one thing that matters: continuity. Being able to carry an exact coding session from Claude Code or Codex into another agent removes a huge amount of friction. The future isn’t starting over with every AI tool. @jarvixdotlive

The model is replaceable. The working session should be portable. Otherwise a multi-agent stack is just a graveyard of separate chat histories.

这个接续思路挺顺，省得来回翻上下文了

This is absolutely gold 💯 I used to get the session summary & hope that new harness would atleast infer 40% of what all happened. Life is easy now

Is this only on terminal? Can you do this on Hermes desktop or on a discord?

This is something I need

Nice. I’ve been using AI chat exporter from chrome extensions

@_can1357 need this for omp!

Can easily be done without changing harness in 👌

ok, that's cool.

@tonbistudio you’re a legend.

I used to restart cold and re-explain the whole repo. Resuming the Claude session with context intact is what actually saves me time.

Awsome

This is the right kind of migration primitive. The important bit isn’t the command, it’s preserving conversation state so the harness can change without resetting the task. Session portability should be a first-class eval dimension.

Love the bridge between tools. Once an agent can carry work across sessions, it’s worth checking what access it carries too.

Wow

Read my mind!

What if you have multiple conversations going and want to import a specific one? There should be an option to provide the conversation ID or topic

Love this — resuming the exact same session across agents removes so much friction from daily coding workflows. Context continuity between tools is exactly the kind of thing that usually requires brittle manual handoffs, so seeing it solved this cleanly is great. ❤️ #zypho_ai

does `hermes --resume` restore tool state too, or just the conversation context from Claude and Codex?

Holy smokes

Insanely useful!

this is the kind of interoperability agents need switching tools is way less painful when the context comes with you