Roadmap · updated 3 Sept 2026

Where this goes, in order.

One person builds this. The order is a promise; the dates are guesses. Local first: everything below starts on your Mac, and the cloud arrives as a place to send a process, not as a login. What ships is listed at the bottom, with the release it came in.

Building now

The early build, in your hands

Sept 2026

A signed app for Apple silicon Macs, sent to the waitlist in the order people joined. Early means early: things will be missing, and the ones that are there work.

The board

Sept · Oct 2026

Describe the result; the agent lays the process out as steps on a canvas. Script steps run the same every time, agent steps take the judgement calls, and it stops where a person should decide. Today a process is a markdown plan you mention in the chat, and it already runs; the canvas, the trace per step and the proofs wired to each step are what is being built.

Snapshots

Oct 2026

Freeze a copy at a checkpoint and come back to exactly that state. Then start N copies from one snapshot, so every run begins from the same place.

Next

Reproducible copies from a flake

Q4 2026

The environment declared once in flake.nix: how to launch the app, which toolchain, which services. Every copy identical, on every Mac.

Run many, check the work

Q4 2026

Copies checking other copies: replay the result, compare two branches pixel by pixel, flag what does not hold. The agent judges with a confidence; you decide when it is not sure.

Promote a process to the cloud

early 2027

A process you designed on your Mac runs somewhere else, on the same kind of copy, while your laptop is closed. The first thing that will cost money.

Later

An address of its own

2027

An agent in the cloud gets a name, alice.its.computer, and an inbox, alice@its.computer. Reach it from Claude, ChatGPT or plain mail; it writes back when it is done or needs a decision. Nothing you design is published unless you say so.

A catalog you can add to

2027

Today the apps come from a shared store, identical in every copy. Later: bring your own, and share a copy definition with someone else.

Shipped

Otto, in the browser

Sept 2026

The cube on the landing answers questions about its.computer from the docs, with a small model running in your browser over WebGPU. Nothing you type leaves the page.

An agent harness with a wheel

Aug 2026

A goal-driven loop, with pause, steer and cancel at any step. You type the goal in a chat; the agent works inside the copy and you watch it in a real window.

An MCP server for the copies

Aug 2026

Any agent that speaks MCP drives a copy: spawn, screenshot, click, type, exec, steer. Claude and ChatGPT out of the box, or a model running on your own Mac.

A real desktop per copy

2026

Isolated Linux GUI apps in microVMs, each with its own Wayland compositor, rendering on the Apple GPU: Chromium, Firefox, Blender. Several side by side in a tiling workspace. Your project folder mounts read-write into the copy.