StackMap
Subscribe
Explore / comet
zeronsh

comet

Zeron: control Claude Code, Codex, Cursor, Grok, Hermes and Pi from a local Rust daemon — sessions live on the device, with optional sign-in to drive them from another machine.

1,097 123 Rust MITupdated yesterday
View on GitHubDispute this mapping →
Curator's take

The pick when you want agent sessions that outlive the laptop lid: a per-device engine owns the data directory, a fresh install is local-only with no account and no network, and signing in adds a synced workspace you can start on one box and follow from another — a VPS keeps agents working after you close the laptop. The profile boundary is unusually honest: login and logout refuse to touch credentials while an engine holds the data dir, and signing in never uploads or imports your existing local sessions. Caveats: the repo is named comet but the product is `zeron`, Linux installs via a `curl | sh` daemon, macOS wants the desktop release or a source build, and it's young enough that the docs are the architecture file.

Mapped by ShipWithAI editors · links verified
README.md

Zeron

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

Zeron driving a Claude Code session with a live branch diff sidebar

Every device runs a small engine that stores sessions on that device. A new installation starts in local-only mode without an account or a network connection.

Install and run locally (Linux)

curl -fsSL https://zeron.sh/install.sh | sh
zeron status

The installer starts the daemon immediately and keeps it running across reboots. No sign-in or sync configuration is required.

Day-to-day:

zeron status      # local/synced mode and engine status
zeron update      # update to the latest release
zeron daemon start|stop|restart|status

Optional multi-device sync

Sign in only when you want to open your account's synced workspace. Authentication changes the profile selected by the next engine start, so stop the daemon before changing it:

zeron daemon stop
zeron login
zeron daemon start

You can then start an agent on one synced device and follow or drive it from another. An always-on machine such as a VPS can keep those agents working after you close your laptop.

Signing in does not upload, move, or import existing local sessions. Local sessions and their attachments remain under the local profile and reappear when you return to local-only mode:

zeron daemon stop
zeron logout
zeron daemon start

zeron login and zeron logout refuse to modify credentials while an engine owns the data directory. The desktop app follows the same next-restart profile boundary.

On macOS: use the desktop release, or build zeron from source and run zeron daemon install to install the launchd service.


Developing or curious how it works? Ask DeepWiki or check out ARCHITECTURE.md.

Licensed under the MIT License.

Continue your stack

What teams reach for next — and why each earns a place beside comet. Ranked by curator confidence.