# witcheer's Wingtips #65: hermes sessions import

Written by [witcheer](https://x.com/witcheer) at Nous Research. Republished with credit.

Canonical: https://hermeswatcher.com/wingtips/65  
Published: 2026-09-07  
[Original](https://notwitcheer.github.io/hermes-recipes/wingtips/65-hermes-sessions-import/) · [On X](https://x.com/witcheer/status/2096849498173530284) · [Full collection](https://notwitcheer.github.io/hermes-recipes/) · [Official docs](https://hermes-agent.nousresearch.com/docs/user-guide/sessions#importing-sessions-from-claude-code-and-codex-cli)

[Source Markdown](https://raw.githubusercontent.com/notwitcheer/hermes-recipes/8653fb699a137a32e81936fa33cabacd3f4f2095/docs/wingtips/65-hermes-sessions-import.md): use this file as the base for relative links in the verbatim text below.

Sources: [Hermes docs: Sessions](https://hermes-agent.nousresearch.com/docs/user-guide/sessions#importing-sessions-from-claude-code-and-codex-cli)


Hermes Wingtips #65: `hermes sessions import`

if you have a conversation going in Claude Code or Codex CLI, you can carry it on in Hermes Agent.

say you spent an hour with another coding agent on a feature, and now you want Hermes to take the next step with all of that context. instead of explaining it again from scratch, you bring the conversation over.

`hermes sessions import`

it lists the sessions it finds on your machine, newest first. pick one and it becomes a Hermes session you can resume like any other.

what comes across is the conversation itself: your messages, the answers, and a short note wherever a tool ran. your other agent's files are only read, never changed.

this is different from `hermes import-agent`, which moves your setup (instructions, skills). this one moves the chat.