Nucleic
Support

Nucleic Help Center

How-to guides for running agents safely — isolating them in Nucleic Control, sandboxing their work, and giving each one a whole macOS virtual machine of its own. Pick a topic below.

Nucleic Control

The hardened path where Nucleic clones, sandboxes, and observes a project directly — the foundation for unattended work, Autoship, and Orchestra.

What is Nucleic Control?

What Control does, how to turn on the container service, and what it unlocks — sandboxed sessions, certain git observation, Autoship, and Orchestra.

Sandboxes

Every sandboxed session runs in its own lightweight Linux VM, built on Apple's containerization framework — isolated from your host and from other sessions.

How agent sandboxing works

What the sandbox is, what it isolates, the per-project options (idle timeout, host exec, custom images), and why the Swift toolchain lives in a VM instead.

Virtual Machines

Give an agent a whole Mac of its own — a per-session macOS VM for Xcode, the simulators, and codesign, so parallel Mac builds never collide on your host.

macOS virtual machines: overview

What macOS VMs are, the hardware and disk requirements, how per-session VMs are cloned and torn down, and how many run at once.
Building the base image

The one-time golden base install: what the build does, choosing a guest macOS version, and pointing at a prebuilt bundle or a specific restore image.
Computer use for macOS VMs

Let an agent see and drive the VM's screen — clicks, keys, and scrolling. The default path runs host-side with no in-guest setup and no permissions.
Setting up AX-based computer useAdvanced

The optional in-guest agent for semantic control — act on a UI element by identity, and inspect an app's accessibility tree. Fully automated on macOS 27.

Can't find what you need?

These guides grow alongside Nucleic. If something is missing or unclear, email hello@nucleic.blakeslee.xyz and we'll help.