Control is the fleet’s brain — the sandboxes, the machines, and the ground Nucleic owns. Agents work sealed off from your Mac, every move they make is accounted for, and a whole Linux box or a whole Mac is on call when a job needs one.
Hand Nucleic a repo and it takes the whole thing off your hands. From then on you get two things you can’t get by pointing an agent at a folder: agents work sealed off from your Mac, so nothing they run can reach your machine — and you know exactly what they did to your code, commit by commit, as it happens rather than after the fact. No firewall prompts, no open ports, no trust required.
Most work belongs in a fast, disposable Linux sandbox that starts in seconds. Some needs more: a full Linux VM with its own kernel, or an entire Mac an agent can build on, look at, and click through. Control picks the lightest thing that can do the job — and throws it away when the job is done. See the machines →
Because a Control project is contained and its work is observed for certain, Nucleic can safely automate what would otherwise be reckless — Autoship merging finished branches, Orchestra fanning one request out into a fleet, and nvrsion putting many agents on one shared trunk. Point an agent at an ordinary folder and you get none of it.
Each session’s work happens inside an isolated machine, not loose on yours.
You get the real record of what an agent did — not an after-the-fact reading of its transcript.
Agents reach Nucleic without ever touching the network — nothing to firewall, nothing to leak.
The one path where Autoship, Orchestra, and nvrsion can safely run.
Nucleic is in open beta. All it asks is macOS 27 on Apple Silicon.