wisp Grid · grid.trywisp.dev

Close the laptop.
Your agents keep going.

Your own wisp, running on a server. Start Claude Code, Codex or opencode on a task, shut the lid, and read the report from your phone. Same app, same reports, nothing to keep awake.

Continue with GitHub
Nothing to installYour own agent accountsInvite only
you.grid.trywisp.dev
wisp: tasks running and waiting for you
Laptop open18:40
Migrate billing to the new APIrunning
Add e2e tests for checkoutrunning

Flip the switch: the laptop sleeps, your grid doesn’t.

Signs in with your own accounts
  • Claude Code
  • Codex
  • opencode
  • Cursor
  • GitHub

01 · HOW IT WORKS

Three minutes from here
to your first task.

1

Sign in

With GitHub or Google. You get your own wisp at you.grid.trywisp.dev, in a box nobody else can touch.

GitHubGoogle
2

Connect your agents

Sign in to Claude Code, Codex and GitHub from Settings → Agents: a link and a code, no terminal. Only what you sign in to shows up.

Claude CodeCodexgh
3

Send tasks from anywhere

From the browser, from wisp on your computer (Settings → Cloud) or from the phone app. It sleeps when idle and wakes for you and your schedules.

BrowserDesktopPhone

02 · WHAT YOU GET BACK

The report,
not the transcript.

you.grid.trywisp.dev
A wisp report: what changed, the diff, the tests

What changed and why

Each task ends with a short brief: the diff that matters, the tests it ran, the numbers that moved, and what it couldn’t do.

It asks when it must

A question or an approval waits on the card, and on your phone, until you answer. Everything else just runs.

Ship it from the card

Every task works in its own branch. One click commits, pushes and opens the pull request with your GitHub.

Follow up in one line

“Now add the same to RefreshQueue.” It picks up where it left off, with its context.

03 · PRIVATE BY DESIGN

Your box, your keys.
Nobody else’s agents next door.

wisp runs your agents with real permissions, so every person gets a sandbox of their own on this grid, and nothing of yours leaves it.

Its own sandbox

Your wisp runs in its own gVisor container: its own kernel boundary, filesystem and network. Other users can’t reach it.

Logins stay yours

Claude, ChatGPT and GitHub sign in inside your box and stay in your folder. The grid never sees a password.

Sleeps when idle

Nothing running, nobody looking: it stops, and wakes in seconds when you open it or a schedule is due.

Open source

The whole grid is in the wisp repo (MIT). Rather host it yourself? One command on any Linux box.

$ npx wisp-agents grid init --domain wisp.example.com

Leave the agents working.
Go have dinner.

Continue with GitHub
Nothing to installYour own agent accountsInvite only