Skip to content

Machines, the Grid and wisp Cloud

Every computer that runs wisp is a machine. Your wisp can start tasks on the others, and all their tasks show in one list. A desktop at home keeps working while your laptop sleeps.

How When
SSH A computer you can already ssh to. wisp installs itself there.
A wisp Grid Each computer signs in to the same grid, which connects them. No SSH, no open ports.
wisp Cloud The grid at grid.trywisp.dev: sign in and you also get a cloud computer.

Add a computer over SSH

Turn on SSH on the other computer (on a Mac: System Settings → General → Sharing → Remote Login; on Linux: openssh-server).

Click the person button in the top bar → Machines (or ⌘K → Settings → Computers → Machines). Type its SSH address (you@studio.local, or a Host from ~/.ssh/config), give it a Name, then Add and connect. The first time, type your password for that computer once; wisp sets up a key so it won’t ask again.

In the browser (wisp --browser, or your cloud wisp) it’s the same window, menus and keys.

Settings → Machines: add a computer over SSH, Tailscale, and Reach this computer from anywhereSettings → Machines: add a computer over SSH, Tailscale, and Reach this computer from anywhere

Or declare it:

machines:
studio: { transport: ssh, address: you@studio.local }

Not on the same network? Install Tailscale on both computers and use the name it gives.

Add a computer through the Grid

Sign in to the same grid on each computer. They find each other through it.

⌘K → Settings → Computers → Cloud → Sign in to a wisp Grid, with GitHub or Google. Then This computer on the grid turns this computer on, so your other wisps and your phone reach it.

Run there

In New task’s footer, click This computer and pick the machine. On a running task, Runs on by the reply box moves the task, its branch and its history to another computer.

To keep work on one machine: machine: studio on a crew member, on: studio on a workflow step. A delegate can run on another computer than its lead, on a copy of the lead’s work; its changes come back when it finishes.

wisp Cloud

Sign in at grid.trywisp.dev and you get your own wisp on a server, with Claude Code, Codex and Cursor installed. It works while your computers sleep. Use it in the browser, from the phone app, or as one more machine in your app. It sleeps when nothing is going on and wakes when you open it.

Terminal window
wisp cloud status
wisp cloud accounts # each grid account signed in to here
wisp cloud switch <account>

Sandboxes

A sandbox is a box of its own on your grid, for one piece of work. The agent can install, run and break anything there, never on your computer. It’s deleted with its task.

In New task’s footer, click This computer and pick Sandbox, or start the prompt with /sandbox. ⌘K → Settings → Computers → Sandboxes signs Claude in once for every sandbox, sets the Env vars they all get, and lists Your sandboxes.

Sandboxes run on your own subscriptions. A delegate, a crew member’s jobs and a goal’s judges can work in one too.

Run your own Grid

A Grid is wisp for many people on your server. Try one on your computer, then run it for real:

Terminal window
wisp grid dev # a grid here, for trying it out
wisp grid serve --data /srv/grid # a real grid, from /srv/grid/grid.json, behind a reverse proxy

A real grid signs people in with GitHub, Google or OIDC, and runs each person’s box as a container. People then sign in with wisp cloud signin https://grid.example.com.