comet vs tailclaude
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 — Claude Code from any browser via your Tailscale tailnet — streaming chat UI, session history, model switching and cost dashboards; no SSH, no terminal.
Both answer 'reach my coding agent from elsewhere'. tailclaude does it with a browser over your Tailscale tailnet and no daemon to run; Zeron does it with a synced engine on each device and a native app.
| comet | tailclaude | |
|---|---|---|
| Stars | 1.1k | 255 |
| Forks | 123 | 26 |
| Language | Rust | TypeScript |
| License | MIT | — |
| Last activity | yesterday | 5 months ago |
| Topics | coding | coding |
| Curated connections | 4 | 3 |
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.
tailclaude — the curator's take
The 'doom coding from your phone' setup without the terminal: publish Claude Code to your tailnet, scan a QR code, get a touch-optimized chat UI with streaming, full session history and cost dashboards — Tailscale handles auth and transport, so nothing new is exposed. The caveats are serious though: the repo ships NO license (all rights reserved by default — you can run it, not fork or redistribute), it's young (~200 stars) and has been quiet for months. Treat it as a clever pattern to evaluate, NOT infrastructure to depend on.