Zeron

Detailed report

Zeron keeps coding agents on your machines and provides native clients for computers and phones. Remote control requires hosted sync. Direct SSH or LAN attachment is not supported.

Research checked November 13, 2026. This is a source-based assessment, not a hands-on product test.

Product and workflow

The product is Zeron at zeron.sh, linked directly to zeronsh/zeron on GitHub. This distinguishes it from the cybersecurity company at zeron.one and trading product at zeron.fi.

Zeron lets you keep your preferred agents and hardware while controlling their work through one interface. You could leave Claude Code working on a Linux devbox, inspect progress from another laptop, and answer a question from your phone. Its Rust interface uses GPUI, the UI technology associated with Zed. The official site also advertises extensibility through plugins. Official product site

That makes Zeron particularly relevant when device switching and scattered terminal sessions are your main frustrations. It supplies the workspace around agents rather than requiring you to adopt another coding agent.

Agents, models, and authentication

The repository names Claude Code, Codex, Cursor, Devin, Grok, Hermes, Pi, and Antigravity. Current source additionally registers OpenCode, fx, Muse Code, and agents added through an ACP registry. ACP is a protocol through which applications communicate with agents. These are integration claims and source evidence. They do not establish equal reliability across platforms. Agent registry source

Models depend on the selected agent, installed runtime, and authenticated account. There is no defensible single, permanent Zeron model list. Likewise, support for OpenCode or Pi does not prove every backend those tools support works correctly through Zeron.

Both subscription authentication and API keys are documented for Cloud’s Claude Code and Codex integrations: Claude/ChatGPT sign-ins or Anthropic/OpenAI keys. Model access and charges remain tied to those accounts. Cloud requires its own connected accounts. A local login alone does not configure it. Cloud implementation document, marked October 1, 2026

Your machines, remote control, and persistence

Desktop downloads cover Apple-silicon macOS, Windows x64, and Linux x64/arm64. Android has an APK. IPhone and iPad have an actual App Store listing. Older reviews saying iOS is “coming soon” are outdated. Mobile is a companion interface: agents execute on a connected computer or cloud machine.

For your headless servers, Linux support is explicit. The installer starts a background engine configured to survive reboots. Optional sign-in lets another device follow or drive its sessions. Existing local sessions are not automatically uploaded when you enable sync. Official README

The architecture separates the interface from the engine. Closing the desktop interface normally leaves the engine and sessions running. Reopening reconnects. Commands can queue while disconnected. However, a service restarting after reboot does not establish that every interrupted agent process resumes seamlessly. That needs testing. Architecture

The critical limitation is no supported direct SSH/LAN host attachment. Issue #1061 requested that capability on October 26, 2026. A contributor closed it as “not planned” on November 9, explicitly directing remote-machine users to the headless engine plus sign-in sync. Thus, owning the server does not eliminate Zeron’s dependence on a hosted control service. Remote-host issue and response

Sync uses Cloudflare-hosted rooms and relays. Terminal traffic can use a direct device connection with relay fallback. This is not equivalent to a general SSH execution architecture. A supported self-hosted backend contract is explicitly deferred. Architecture

Vendor Cloud is separate: each session gets a hosted sandbox, clones an authorized GitHub repository, sleeps when idle, and wakes on another message. Documented v1 agents are Claude Code and Codex. Child chats share their parent’s sandbox and files. Cloud design

Isolation, review, and orchestration

Zeron supports optional Git worktrees, which provide separate folders and branches for concurrent tasks. It also provides live diffs, terminals, account switching, and steering or interrupting runs. The project’s parity checklist marks worktree controls and remote worktree operations implemented. Worktrees separate edits. They are not a security sandbox. Implementation checklist

The PR interface contains review states, mergeability and CI assessments, and attention grouping. This is substantive GitHub workflow integration, although source inspection alone cannot validate the complete experience. PR interface source

Native subagents and agent-created side chats are represented. Still, do not equate multiple sessions with a proven autonomous planning, scheduling, and verification system. “Goal mode” was an open feature issue dated November 9. Tests can run through agents and terminals. I found insufficient evidence for universal mandatory test or approval gates. Current issue tracker

Setup, security, and cost

Prebuilt desktop packages are the practical starting point. On Linux servers, the README supplies an installer and status, update, and daemon commands. Agent executables and their authentication remain separate setup dependencies. The project is MIT licensed. README

The privacy policy, effective October 26, 2026, states that synced transcripts include prompts, replies, tool output, and diffs. They are encrypted in transit and at rest, not end-to-end encrypted. Zeron’s systems can technically read them. Cloud also stores encrypted provider credentials and processes billing through Stripe. Agent providers receive code under their own policies. Privacy policy

Same-account devices can read and write one another’s workspace files. Treat account enrollment as granting significant machine access, particularly where repositories contain credentials.

Pricing has an important evidence gap:

• Local software: free/open source. No paid local licence requirement found.
• Hosted sync: no verified public fee schedule or published limits found.
• Cloud: billing and usage credits exist, but I could not verify current currency prices, plan allowances, or pack prices.
• Models and infrastructure: your provider subscription/API usage and your own server costs remain separate.

Cloud documentation defines one credit as one minute of a small machine, with larger-machine multipliers. Do not interpret “open source” as unlimited free hosted compute. Cloud metering

Development and user reports

Development is active: GitHub lists v0.3.2 on November 12, 2026, alongside v0.3.0 and v0.3.1 that day. The repository showed roughly 3,500 stars. Frequent releases demonstrate activity, not stability. Releases

Positive reactions emphasize smoothness, appearance, and responsiveness. However, most accessible examples were selected for Zeron’s homepage. They are vendor-curated testimonials, not broader user satisfaction. Selected testimonials

More concrete limitations include:

• A November 12 user report describes repeated GNOME Wayland interface exits on v0.3.0 while the background engine remained running. This does not prove v0.3.2 has the same fault. Issue #1388
• An independent reviewer reports September 24 source-build and test attempts timing out after 900 seconds while compilation continued. That indicates build burden in that environment, not failed test assertions. MrKeyoor’s report

The App Store has insufficient ratings for an overview. Public evidence is too sparse to establish broader user satisfaction.

Fit and trial

For this workflow, Zeron deserves a trial if a persistent server engine and cross-device supervision matter more than direct SSH attachment. Avoid it if remote control must remain entirely within your own network.

Teams may benefit from consistent interfaces and PR visibility. I did not verify mature role-based permissions, audit controls, or safe shared-server tenancy. Same-account device trust should not substitute for individual team authorization.

Use a disposable repository on a Linux server with two laptops and a phone. Run Claude Code and Codex in separate worktrees, close both laptops, and reconnect from mobile. Review diffs and CI results. Test network loss, engine restart and server reboot separately. Check Cloud’s actual checkout prices separately. Success means retained work, correct execution host, predictable reconnects, and acceptable data exposure.

Comparison facts