Guide
Use wisp Cloud
To keep coding agents working when your laptop is closed, run them on a computer that stays on. wisp Cloud gives you one: your own wisp on a server, in a sandbox of its own, that you open from the browser, from wisp on your computer, or from your phone. It’s free in early preview at grid.trywisp.dev, a few accounts at a time, and you can run the same thing on your own server.
wisp Cloud: free during the preview, sign in with GitHub · or run wisp on your own computers, MIT
1. Sign in
- Open grid.trywisp.dev and press Continue with GitHub.
- Your account page shows your cloud computer at
you.grid.trywisp.dev. Press Open wisp: it starts in a few seconds, and you’re in the same wisp you know, in the browser.
2. Connect your agents
Your cloud computer comes with Claude Code, Codex, opencode and gh installed. Sign them in with your own accounts: in your cloud wisp, Settings → Agents → Sign in.
- Claude Code: open the sign-in page, sign in with your Claude account, and paste the code it shows back into wisp.
- Codex: open the page and type in the code wisp shows (it runs
codex login --device-authfor you). - GitHub: the same, with
gh auth login. Afterwardsgitpushes with it and commits carry your GitHub name, so Ship it opens pull requests.
The logins stay in your own folder on the server. The model picker only offers the agents you signed in to; opencode’s free models work with no account at all.
3. Use it from your computer
- In wisp on your computer, open Settings → Cloud (or Machines → Or use a cloud computer). The address is filled in: press Sign in.
- wisp shows a code and opens grid.trywisp.dev. Check the code and press Allow.
- Your cloud computer joins Run on next to this computer and your SSH machines. Settings → Cloud also lists its agents with Sign in buttons, so you can sign them in from here.
Watching it from your desktop doesn’t keep it awake. When it sleeps the card says Asleep, its tasks still show, and anything you send it wakes it.
4. Use it from your phone
The wisp Android app starts with wisp Cloud on its first screen: press Sign in, allow the code in your browser, and your cloud computer opens in the app. No SSH and no tunnel to set up.
What’s private
- A sandbox per person. Your wisp runs in its own gVisor container, with its own folder and network. Other people’s wisps can’t reach it, and neither can it reach theirs or the server itself.
- Your logins stay yours. Claude, ChatGPT and GitHub sign in inside your box. The grid never sees a password.
- It sleeps when idle and wakes for you, a task, or a schedule.
- Delete your account and your folder and its keys are gone.
Questions
- Is wisp Cloud free?
- Yes, during the early preview. You bring your own Claude, ChatGPT or GitHub accounts; model usage is billed by those providers.
- Why can’t I sign up?
- The preview runs on one small server, so it takes a set number of accounts. When they’re all taken, the sign-in page says so and trywisp.dev/cloud.html takes your email for the next free seat. People who already have an account keep signing in.
- Do I need wisp installed on my computer?
- No. The browser is enough. wisp on your computer and the Android app can sign in to it too, with a code.
- Can I run my own?
- Yes: the grid is in the wisp repo (MIT). See Run your own wisp Grid.
- What happens to a task when the cloud computer sleeps?
- It only sleeps when no task is running and nobody is looking. Tasks, reports and logins are kept; it wakes in seconds.
Related guides
- Run Claude Code 24/7 without a VPSKeep Claude Code and Codex working with the laptop shut: rent and run a server, or open a free box on wisp Cloud.
- Run your own wisp GridOne small Linux server, a GitHub or Google sign-in, and every person gets their own sandboxed wisp.
- Run coding agents in the backgroundHeadless runs that can still ask you, notify you, and report back in one screen.