Which Claude plan do I need?

Your own, the same as on your laptop: Claude Code signs in with your Claude account. wisp doesn’t resell model usage, so your plan’s limits apply wherever it runs.

What happens when I close the laptop mid-task?

On wisp Cloud, nothing: the task runs on the server. Your box only sleeps when no task is running and nobody is looking, and it wakes in seconds when you open it, send a task, or a schedule is due.

Is wisp Cloud really free?

Yes, during the early preview. It runs on one small server, so it takes a set number of accounts; the Cloud page says how many are left, and when they’re taken you can leave your email for the next one.

Does it work for Codex and Cursor too?

Yes. Codex, Cursor, opencode, Grok and Antigravity are installed next to Claude Code, each signs in with a link and a code, and one queue holds all of them.

Guide

Run Claude Code 24/7 without a VPS

Claude Code runs where you start it, so it stops when your laptop sleeps or the SSH session drops. To keep it going overnight it needs a computer that stays on. You can rent one and run it yourself, or open wisp Cloud and get your own box with Claude Code, Codex and Cursor already installed, free during the preview.

Try wisp Cloud

wisp Cloud: free during the preview, sign in with GitHub · or run wisp on your own computers, MIT

Why it stops

A coding agent is a process on the computer you started it on. When that computer sleeps, the process sleeps; when your SSH session drops, the process goes with it unless something like tmux holds it. Driving it from your phone doesn’t change that: the run still lives on the machine that has to stay awake. So the fix is a computer that never closes its lid.

Option 1: run your own server

Rent a small Linux VM. 2–4 GB of RAM is a floor once the agent runs your builds and tests.
Set it up: a user that isn’t root, Node.js, Claude Code, git and gh, and your repo cloned.
Sign in on the server with claude auth login: open the link it prints and paste the code back.
Run it inside tmux so it survives the connection dropping, and attach from your phone’s SSH app.

ssh you@your-server
tmux new -s agent      # keeps running when the connection drops
claude                 # sign in once with: claude auth login

# later, from your phone's SSH app
tmux attach -t agent

It works. What you get on the phone is the terminal: the transcript, permission prompts and diffs at phone size. You also keep the box patched, watch its disk, update the CLIs, and do it all again for Codex.

Option 2: wisp Cloud, nothing to set up

Open grid.trywisp.dev and press Continue with GitHub. You get your own wisp at you.grid.trywisp.dev, in a gVisor sandbox of its own.
Sign in to Claude Code from the model picker or Settings → Agents: a link to Claude’s own sign-in page and a code, no terminal. Codex, Cursor, Grok, Antigravity and gh sign in the same way; opencode’s free models need no account.
Give it a task and close the laptop. It keeps running. Questions and the finished report reach you in the browser, wisp on your computer, or the Android app.

The preview is free. It runs on one small server, so it takes a few accounts at a time: the Cloud page says how many seats are left, and takes your email when they’re gone. The full walkthrough is in Use wisp Cloud.

Side by side

	Your own server	wisp Cloud
Setup	A VM, a user, Node, the CLIs, sign-ins, tmux	Sign in with GitHub, then sign in to Claude Code with a code
Cost	The VM every month, plus your Claude plan	Free during the preview, plus your Claude plan
Agents	The ones you install	Claude Code, Codex, Cursor, opencode, Grok and Antigravity, installed
From the phone	An SSH app and a terminal	wisp in the browser or the Android app: cards, reports, a button per question
When the agent asks	It waits in the terminal until you attach	A notification; answer from whichever device you’re on
When nothing runs	The VM stays up	It sleeps, and wakes in seconds for you, a task or a schedule
Upkeep	OS patches, disk, CLI updates	None on your side

Option 3: a computer you already have

A desktop or home server that stays on works too. wisp’s Machines starts the agents there over SSH from your laptop, and every run lands in the same queue: agents on multiple machines. For a team, run the same server wisp Cloud runs on: run your own wisp Grid.

Questions

Which Claude plan do I need?: Your own, the same as on your laptop: Claude Code signs in with your Claude account. wisp doesn’t resell model usage, so your plan’s limits apply wherever it runs.
What happens when I close the laptop mid-task?: On wisp Cloud, nothing: the task runs on the server. Your box only sleeps when no task is running and nobody is looking, and it wakes in seconds when you open it, send a task, or a schedule is due.
Is wisp Cloud really free?: Yes, during the early preview. It runs on one small server, so it takes a set number of accounts; the Cloud page says how many are left, and when they’re taken you can leave your email for the next one.
Does it work for Codex and Cursor too?: Yes. Codex, Cursor, opencode, Grok and Antigravity are installed next to Claude Code, each signs in with a link and a code, and one queue holds all of them.