Oh My Pi session sync — continue on any device

Last updated 2026-09-17 · MIT licensed · free for personal self-hosting

Oh My Pi (client id omp) keeps a very clean store: one directory, a set of append-only files, and therefore the most straightforward sync path of any agent here.

Where Oh My Pi keeps its sessions

Item Value
Directory ~/.omp/agent/sessions/
Override set OMP_CODING_AGENT_DIR and the adapter follows it

If you have relocated Oh My Pi's data directory (say, onto a second drive), set OMP_CODING_AGENT_DIR and the adapter reads it there.

Connecting it

  1. Open the setup help page, pick Oh My Pi, and download the client package (server address pre-filled).
  2. On first run, execute install-deps.bat (Windows) or ./install-deps.sh (macOS / Linux).
  3. Register with the generated command — your workspace API key is already filled in. The client starts as HERMES_SYNC_AGENT=omp.
  4. Restart Oh My Pi.

First start pulls incrementally; an empty server gets a full push to complete the pairing; then it syncs every 5 minutes.

Behaviour worth knowing

  • Append-only — sessions are appended to, never rewritten or reordered, so your existing history stays exactly as it is.
  • Titles travel with the sessions — title / title_change entries are session data, so the list on your second machine shows the same names instead of a wall of untitled entries.
  • uuidv7 session ids — time-ordered by construction, so merging two machines' worth of sessions never collides or reshuffles.

Across devices, across agents

This is the classic setup: one machine at home, one at the office, both running the Oh My Pi client against the same workspace. Ask half a question at the office, open the same agent's session list at home, and keep going. Or continue in Hermes or OpenCode — the pool is shared.