NucleicnarOS
In development

narOS

An operating system
built for agents.

Every OS your agents work on today was designed for a person at a keyboard. narOS wasn't. It's built from the ground up for the thing actually typing — tools already installed, caches already warm, permissions already sorted — so the first turn is the actual work, and what passes in one place passes everywhere.

narOStools · caches · permissionsready before the agent asksa quick sandboxa container it spun upa cloud runnera full Linux VMwherever the work lands · the same machine
Scroll
One fleet, one machine

Works here means
works everywhere.

A quick sandbox, a cloud runner, a container an agent spun up for itself, a full Linux VM — as far as your agents are concerned, they're all the same machine. A green run means something, because it wasn't luck about where the job landed. And "it only breaks on the runner" stops being a thing you spend an afternoon on.

TO BUILD WITHevery majorlanguagecompilers andbuild toolsTO WORK WITHsearch, inspect,transformthe tools everysession reaches forALREADY SORTEDcaches warmpermissions granteda screen to drivenothing to install…and anything else, one command away
waiting on arrival, every time
Turn zero

The first turn is
the actual work.

Every turn an agent spends hunting a package name, waiting on a toolchain, or arguing with permissions is one you paid for and got nothing from. narOS has already answered all of it: the languages are there, the tools every session reaches for are there, installs come back fast, and sudo just works. Your agent opens the file you asked about instead of asking where things are.

BEFOREwhich node?apt-get updatepermission?retry…WITH narOS$ the actual worksetup is our problem, not your agent's
turns spent on setup → zero
No human in the loop

Nothing sits waiting
for someone to type.

A desktop OS is full of moments that quietly assume a person is watching: a prompt that wants y, a pager that never exits, a dialog behind the window. Each one is an agent stuck until something times out. narOS is built the other way around — no interactive stalls, no invented TTY, and errors written to be read by the thing that has to fix them: what failed, and what to do about it.

BUILT FOR A PERSONDo you want to continue? [Y/n] _…waiting…BUILT FOR AN AGENTerror: port 5432 already bound by pid 812fix: stop it, or set PGPORT to a free port
an answer an agent can act on, first try
Nothing to switch on

Watched from the
very first command.

Every narOS machine is already reporting. There's no watcher to install, nothing to configure, and no forgotten flag on the one box that turns out to matter. A thirty-second sandbox and a runner that's been up all week give you the same complete record — which is what makes walking away from the work a reasonable thing to do.

Meet nash →

a commanda scripta build stepnashalready watchingyour cockpithowever it starts
no setup step to forget
Why it matters

Ground solid enough to leave your agents on.

Straight to work

Everything an agent needs is already waiting. No setup turns, no tokens burned on plumbing.

One answer, everywhere

Passing here means passing there. Where a job ran stops being a variable you chase.

Nothing unwatched

Every machine reports from its first command. Nothing to enable, nothing to forget.

Theirs to wreck

Let agents install anything and change everything. The machine disappears afterward; nothing they touch is yours.

Keep exploring
Open beta

Give your agents somewhere worth working.

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

No account required · private by design · runs offline