NucleicNucleic Control
Nucleic Control

Repos Nucleic
manages end to end.

Let Nucleic clone and manage a project itself, and its agents run contained and observed — not loose on your Mac. It’s the foundation for work that runs while you’re not watching.

managed clone commit observedmerge observedconflict observed
Scroll
What it does

Contained.
And accounted for.

A Control project lives in a managed location, and everything an agent does to it is contained and known: sessions run sandboxed, git work is observed with certainty, and the link between agent and Nucleic never touches the network — no firewall prompts, no exposed ports.

managed clone commit observedmerge observedconflict observed
managed · sandboxed · observed
What it unlocks

The launchpad for
hands-off work.

Because a Control project is contained and its work is observed for certain, Nucleic can safely automate what would otherwise be risky — Autoship, Orchestra, and nvrsion all build on it. Point an agent at an ordinary folder and you get none of it.

Why it matters

Why unattended work needs Control.

Sandboxed

Each session’s work happens inside an isolated environment, not on your machine.

Observed for certain

Nucleic knows exactly what an agent did — because the work reports itself.

Private control plane

The agent’s link to Nucleic never touches the network.

Automation-ready

The one path where Autoship and Orchestra can safely run.

Keep exploring
Open beta

Let Nucleic hold the repo.

Nucleic is in open beta. All it asks is macOS 27 on Apple Silicon.

No account required · private by design · runs offline