@oharness/sync

The session sync server: stores conversations so a session started on one machine can be resumed on another.

npx @oharness/sync --help

It reads no configuration file. Whatever deploys it — a container's environment, a systemd unit, a platform's variable store — is the only source of configuration, because a sync server that reads a file from the working directory is a sync server whose destination a repository can change.

Tokens are verified by signature rather than by asking an auth service, so nothing on the request path depends on another service being up. Without a signing secret configured it degrades to a self-hosted mode: a users.json and tokens handed out by hand.

Documentation:

• Running your own sync server
• Implementing the Sync protocol