Agent Context Sync

What Agent Context Sync does

Agent Context Sync keeps conversations from Hermes, DeepSeek Harness, opencode, Reasonix, OpenClaw, WorkBuddy and Oh My Pi in one shared pool, held by a self-hosted FastAPI server. A new device pulls the complete history on first pairing, so a session started on one machine is waiting on another, and a thread can be handed from one agent to the next.

Sub-agent conversations fold into their parent session with a badge so the main thread stays readable. Profiles and projects sync across machines, and a team can share a pool with tenant isolation: admins manage users, invites and workspaces but cannot read anyone's sessions. Because every session is pushed to a server you control, history survives a wiped device or profile. The tool offers export and import as Markdown or JSON.gz, a soft-delete trash, and per-session pause and resume of sync. The README is available in English and Simplified Chinese.

Key features

• One shared session pool for Hermes, DeepSeek Harness, opencode, Reasonix, OpenClaw, WorkBuddy and Oh My Pi
• New devices pull the full history on first pairing
• Sub-agent threads fold into the parent session with a badge
• Backup to a self-hosted FastAPI server that you control
• Export and import as Markdown or JSON.gz, plus a soft-delete trash
• Per-session pause and resume of sync

When to use it

• Continuing on a laptop a Hermes conversation that you started on a desktop
• Handing a thread from Hermes to another agent without copy-pasting history
• Keeping a recoverable copy of agent conversations after a drive failure
• Sharing a session pool inside a team while admins cannot read session content

Who it is for: People who use several AI agents across several machines and want one backed-up conversation history.

How it fits with Hermes Agent

It supports Hermes Agent as one of seven listed agents that read and write the shared session pool.

Requirements: A self-hosted FastAPI server that you control to hold the session pool

FAQ