comet vs helmor
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. — versus — Local-first desktop workbench for orchestrating coding agents: per-repo workspaces, task dispatch, live status and runnable actions — GUI plus CLI, Apache-2.0.
Two local-first desktop workbenches for driving coding agents. Helmor organizes per-repo workspaces and task dispatch; Zeron organizes sessions per device and adds multi-device sync. Pick by whether you switch repos or switch machines.
| comet | helmor | |
|---|---|---|
| Stars | 1.1k | 1.3k |
| Forks | 123 | 118 |
| Language | Rust | TypeScript |
| License | MIT | Apache-2.0 |
| Last activity | yesterday | 5 days ago |
| Topics | coding | coding, orchestration |
| Curated connections | 4 | 5 |
comet — the 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.
helmor — the curator's take
Workbench, not factory: you stay the lead and dispatch agents into per-repo workspaces, watching status like a build queue. Cleaner mental model than kanban swarms for a solo dev. Skip for headless issue-queue automation (contrabass) or if you live inside one OpenCode session (codenomad).