01
Ready before the ask
No environment to assemble before useful work begins. The Computer already has a home, tools, and the context you have accepted.
The product we are building
A computer that can
operate itself.
Give it the work already in front of you. It keeps going when your attention moves elsewhere, and you can return from any device to the same work.
Use it directly, address a specialist, or let the Computer choose whatever agent and environment the work needs.
Hand off anywhereLeave when it is safeReturn to the same work
Checkout callback
One piece of work · 9:12–9:31 AM
Safe to leave
Agent Computer · 9:14 AM
Your attention is no longer the runtime.
The work is durable outside the foreground device. Close the laptop or keep using it—the same work continues either way.
Failure reproduced. Fixing it in a worktree and adding the regression test. Next meaningful update in about 15 minutes.
What the Computer kept
- Now
- Repairing the callback
- Next
- Run the auth suite
- Boundary
- Production untouched
Device
Optional
Work
In motion
Computer
Same
Illustrative product story · current alpha capabilities are labeled below
Why it matters
Hand off the work.
Take back your attention.
Powerful agents still make you prepare the machine, move the context, keep the session alive, and explain everything again when the agent or device changes. Agent Computer removes that work around the work.
Your attention may come and go.
The work does not restart.
The work does not restart.
02
Your attention can leave
The product tells you when the required state is durable and the foreground device is no longer the thing keeping work alive.
03
Return without restart
A new device, agent, machine, or moment in time opens the same work instead of another empty session.
04
It compounds into your Computer
Files, logins, tools, routines, accepted decisions, and successful work accumulate instead of disappearing with a chat.
The whole loop
From the thing in front of you
to a verified result.
Handoff is the entrance. Continuity is the product experience. Returning should never mean finding the right session and explaining the work again.
Say it
A request or voice note
Show it
A tab, screen, selection, file, or repo
Send it
A link, email, document, or recording
- 01Give the real contextStart where the work already is instead of rebuilding it inside a new chat.
- 02See what the Computer acceptedIt resolves the real resource, desired outcome, minimum permissions, and continuation route.
- 03Leave or keep steeringWatch closely, disappear completely, or move between the two without changing the work.
- 04Return to a resultCome back from Mac, phone, or Web to the same work, with proof, boundaries, and a restore path.
The meaningful status
You can leave.
Not merely “an agent is running.” The Computer has the context, capability, checkpoint, and authority it needs to continue honestly without your foreground attention.
You
Free to move
Work
Still in motion
What remains
Agents can change.
Your Computer remains.
The durable thing is not an agent session, a model, or a VM. It is the Computer that keeps your world and the work you still expect to become true.
Intelligence can be replaced.
The relationship does not migrate with it.
The relationship does not migrate with it.
01
Computer
The durable owner layer
Your files, identity, accepted context, ongoing work, boundaries, artifacts, and history stay here.
02
Agents
Replaceable intelligence
Claude Code and Codex run in the current alpha. OpenClaw, Hermes, and future runtimes are product direction—not owners of your state.
03
Profiles
Optional addressable context
A coding, support, or research profile can retain its own purpose, skills, permissions, and workspace.
04
Environments
Elastic execution
Isolated VMs, worktrees, containers, or connected machines appear and disappear as the work requires.
One Computer, yours to use
One home. Multiple ways in.
Default entrance
Ask the Computer
Use the simplest path and let it resolve the context, capability, and execution route.
Named profile
Address a specialist
Go directly to the support, coding, or research context when that continuity matters.
Direct operation
Open it yourself
Use the same browser, terminal, files, or native agent CLI whenever direct control is better.
Trust makes autonomy useful
Autonomy without
another thing
to babysit.
You can only leave when the Computer is honest about what it is doing, careful about where it acts, and recoverable when it fails.
01
It keeps the work
A tab, session, worker, or machine can end without silently deleting what the Computer still owes.
02
It acts within exact boundaries
Permissions, spend, publishing, payments, deletion, and production effects stay inside limits you control.
03
It returns proof and a restore path
Done means the artifact or changed state, what was checked, what remains uncertain, and how to recover.
04
It stays yours
Use it directly, export the important state, change the agents underneath, or move the environment without losing your world.
Private alpha
Prove the handoff
with one real thing.
The current alpha starts with Mac and Chrome context into persistent cloud work. The test is not whether another agent can answer—it is whether you can stop carrying the work yourself.
- 01Give it one real contextA browser tab, screen, file, repo, selection, or plain request.
- 02Wait for an honest handoffSee what was accepted and whether the work can safely continue away from this device.
- 03Return and steer the same workCome back on the Web, add direction, and receive the result with proof.
Founder-run · private alpha
Help shape the first Computer.
Available now
- Mac and Chrome context handoff
- Persistent cloud continuation
- Claude Code and Codex execution
- Web return and steering
Building toward
- Ready in seconds with its own identity
- Phone as a first-class companion
- More agent runtimes
- Elastic isolated environments
Product vision and current capabilities are labeled separately.
Questions
The short version.
Is Agent Computer another AI agent?OpenClose
No. It is the persistent computer agents work inside. The Computer keeps your files, identity, accepted context, permissions, and ongoing work while individual agents and machines can change.
What does “return to the same work” mean?OpenClose
The outcome, context, checkpoint, boundaries, progress, and result belong to the Computer—not the tab or model session that happened to start them. A new device or agent should not require you to explain the work again.
Do I have to use one general assistant?OpenClose
No. Ask the default Computer entrance when you want convenience, address a named profile when its particular context matters, or open the Computer yourself. None of those paths creates a new home.
Which agents can it run?OpenClose
The current alpha executes through Claude Code and Codex. The product is being built so additional proprietary and open-source runtimes—including OpenClaw, Hermes, and whatever comes next—can operate the same Computer without owning its durable state.
Does always-on mean every VM runs forever?OpenClose
No. Always-on describes the logical Computer: it remains reachable and keeps the work and state. Isolated execution environments can start, pause, move, or disappear as the work and budget require.
Does it take over my Mac?OpenClose
Usually no. The Mac supplies the context you approve; persistent cloud continuation is the default. If work truly depends on local state, that requirement should be visible, isolated, and narrowly scoped.
What can I try today?OpenClose
The private alpha can accept Mac or Chrome context, continue work in a persistent cloud environment through Claude Code or Codex, and let you return and steer from the Web.
What happens to my files and context?OpenClose
The product is designed around owner-controlled, portable state. Your accepted world belongs to your Computer, not one temporary worker or model session.
Start with one real thing
What work would you stop
carrying yourself?
Tell us the thing already in front of you—something you would like to hand off, leave, and return to only when it needs you or is done.