its.computer — a computer for your AI agent
{{ agentName }}.its.computer early access
its.computer
you · your agents · your processes

Every agent needs a computer. This is its.

Isolated, GPU-capable Linux desktops on your Mac, on your real files. Use them yourself, hand one to an agent over MCP, or design a process once and let it run again — several copies at a time, every window visible, the wheel yours whenever you want it.

{{ waitlistNote }}
sending…
{{ error }}
You're on the list. We'll write when there's a build worth your time.
Two versions of the same app, fully isolated. "Show me what changed" — and it hands back the proof.
workspace — 2 builds · run #418
video — two builds running side by side
screenshot — the proof it was asked for
screenshot — copy #2, the other build

Today it runs on your Mac. Soon it moves to the cloud — with its own address and inbox.

The situation

Some work takes an afternoon, not one prompt.

{{ p.label }}
{{ p.body }}
Design it once, hand it over

You describe what has to come out. Agents do the work that produces it.

lay out the process on a canvas · refine it in chat · run it in N copies
designer — untitled process
source
Your project
repo · branch · rw mount
step
Open the browser
chromium in a copy
step
Run the suite
exec · watch output
check
Capture and compare
screenshot both builds
artifact
Report → ./out
plus a PR comment
decisionneeds you
Ask before choosing
when the two differ
youwhen the two screenshots differ, ask me instead of guessing
↳added a decision node after compare
youput the report in ./out and comment on the PR
↳two destinations wired to the artifact node
runs — same process, three copies
{{ r.copy }} needs you
{{ r.what }}
{{ r.out }}

The workspace and the runs work today. The designer — a canvas where you wire up the steps, the checks and where the artifacts land, and a chat that edits it with you — is what comes next.

How it works
{{ s.n }}
{{ s.title }}
{{ s.body }}
its-computer-vm — spawn · screenshot · click · type · exec · steer
Bring your own agent — Claude Code, a custom loop, anything that speaks MCP. its.computer is the computer, not the brain.
Why it's different
{{ p.title }}
{{ p.body }}
Ways to use it

Developers running coding agents on real projects — and anyone who wants a run that worked to become something that runs again.

Three ways to run it, and you choose how much you hand over. Start with none of it delegated; add design when you want the work to happen without you standing over it.

{{ l.n }} {{ l.title }}
{{ l.body }}
{{ l.cost }}
All three run on your Mac. Nothing needs the cloud yet.
Where this goes

A cockpit now. An address of its own next.

Local, you watch and steer. In the cloud, a copy keeps working while you don't — and emails you when it needs a decision. Further out, the process you designed becomes an actor that takes the jobs it was built for.

{{ r.when }} {{ r.what }}
later {{ agentName }}.its.computer · {{ agentName }}@its.computer — an actor that takes the jobs it was designed for
A process you design stays yours — nothing is published by default.
two things it already does
{{ a.title }}
{{ a.body }}
It's a computer.
Get on the list

Give your agent a computer.

Early builds, warts and all.

sending…
{{ error }}
You're on the list.