Zeron

Control your coding agents (Claude Code, Codex, Cursor, Devin, Grok, Hermes, Pi, Mimir, and Antigravity) locally by default, with optional private multi-device sync.

English | 简体中文

Every device runs a small engine and keeps a local cache. A new installation starts offline and local-only: no account, hosted backend, or provider credential is required.

Install

Linux:

curl -fsSL https://github.com/wasimysaid/Kratos/releases/latest/download/install.sh | sh
zeron status

The installer verifies the GitHub Release manifest and checksum, installs the engine plus its managed Tailcat adapter, and starts a user service when systemd is available.

Mimir connects through mimir acp. Install the mimir CLI on the device that runs the agent; Zeron discovers it in Settings → Agents. The desktop sidebar browser also needs the Linux browser runtime.

Useful commands:

zeron status
zeron update
zeron daemon start|stop|restart|status

On macOS, download the DMG from the latest GitHub Release. On Windows, download the portable ZIP, keep zeron-update.json beside zeron.exe, and see the source-build notes.

Optional multi-device sync

Tailcat provides private connectivity; Zeron's durable peer provides authenticated sync and storage. To support catch-up when laptops are not online together, initialize the peer on an always-on machine such as a VPS:

zeron daemon stop
zeron peer init --name home-peer
zeron daemon start
zeron peer invite --output invite.txt

Transfer invite.txt privately. On another stopped installation:

zeron daemon stop
zeron pair --code-file invite.txt
zeron daemon start

Invitations are short-lived and one-use. Pairing uses persistent device keys and proof of possession; list or revoke trusted devices with zeron peer devices and zeron peer revoke <device-id>. Keep pairing codes and Tailcat addresses private.

Packaged releases include the adapter. Source builds can run scripts/build-tailcat.sh native and set ZERON_TAILCAT_ADAPTER to the resulting binary. Public DERP relays are rate-limited and have no SLA; operators needing durable relay service should initialize with an owned HTTPS DERP map using --derp-map.

Paired devices are trusted with the remotely permitted workspace surface. A controlling device can list, read, and write files on the owning device; enabling ignored-file visibility can expose files such as .env. .git remains excluded.

Sync starts fresh: creating a peer creates a new paired profile; joining an existing peer loads that peer's data. There is no "Bring my work" option, local-session import, or old cloud-account migration. Existing local and historical files are left untouched. Desktop setup switches runtimes in-app; headless users restart the engine. Return to local-only mode with:

zeron daemon stop
zeron logout
zeron daemon start

See ARCHITECTURE.md for the runtime and storage model and docs/peer-backup.md for backup/restore of the new peer.

Licensed under the MIT License.