Skip to content

Cloud computers for the agents you already use.

A Linux computer your agent runs as root. It keeps its files and wakes from sleep in about a second.

Get your boxRead the docs

7-day trial · 10 awake hours · no card

Recordings of real wack boxes: a GPU render, test suites, builds, a headed browser and a pixel diff.

Works with the agents you already use

  • Claude Code
  • Codex
  • Cursor
  • VS Code
  • Gemini CLI
  • Windsurf
  • Any MCP client

Or paste this into your agent. It reads the manual, asks for your connect URL and sets itself up.

Read https://wack.sh/SKILL.md and connect me to wack

A computer that's still there tomorrow.

Screen of a wack box: a terminal that has installed, built and started a small Vite app, and Chrome showing the app while the agent changes its text colour, from a failing 2.81:1 to 7.57:1, which passes every contrast check.

Build

Your agent is root. It installs what the job needs with apt-get, npm or uv, builds it and starts the server. Every install is still there next time.

Screen of a wack box running pytest: 24 property tests pass one by one, finishing in 18.47 seconds.

Test

Long test suites run on the box while your laptop stays free. Python, Node.js, Playwright with Chromium and FFmpeg come installed.

The Boxes page in the wack dashboard: five boxes, each asleep, showing the last lines from its terminal.
The Boxes page in the wack dashboard: five boxes, each asleep, showing the last lines from its terminal.

Sleep

After 10 idle minutes the box sleeps and uses none of your hours. The next call wakes it in about a second, with every file where it was.

How boxes work

  1. Your agent is root. It installs what the job needs with apt-get, npm or uv, builds it and starts the server. Every install is still there next time.

  2. Long test suites run on the box while your laptop stays free. Python, Node.js, Playwright with Chromium and FFmpeg come installed.

  3. After 10 idle minutes the box sleeps and uses none of your hours. The next call wakes it in about a second, with every file where it was.

How boxes work

Your agent makes its own boxes.

One connect URL gives your agent 14 tools. When a job splits into parts, it makes a box for each, runs them side by side and deletes the ones it made.

Real recordings from four boxes: a test suite, a headed browser, a Next.js build and a GPU render.

Three tool calls

  1. box_create{ "name": "build-a", "size": "large", "ephemeral": true }→ build-a · Large · awake
  2. box_exec{ "box": "build-a", "command": "npm ci && npm run build" }→ exit 0
  3. box_delete{ "box": "build-a" }→ deleted

box_create

A new box, set up and awake when the call returns.

ephemeral: true

A throwaway box that deletes itself, with its files, the first time it sleeps.

box_image_save

Saves a set-up box as an image, so new boxes start as exact copies.

All 14 tools

Your plan caps how many boxes exist and how many are awake at once: 2 on Pro, 4 on Power. wack never stops or deletes a box to make room.

Watch it work. Take over any time.

Turn on a box's screen and your agent gets a real 1440 × 900 display with a headed browser. Watch it live from the dashboard.

The Screen tab for box contrast in the wack dashboard, live and view-only, while the agent builds an app and checks it in Chrome.
View-only by default
The Screen tab starts view-only, so you can't disturb your agent by accident.
Take control
Click and type into the box yourself, to sign in to a site or get past a prompt. Your agent carries on from there.
Up to three viewers
Three people can watch the same screen at once.
Watching is free
Watching doesn't keep a box awake. An idle box still sleeps after 10 minutes.
The screen

From 1 vCPU to an RTX 4090.

Your agent picks a size when it makes a box. A standard box suits most work; bigger boxes use your awake hours faster.

An awake hour on Standard uses 1 plan hour

Box sizes
SizeMachinePlans
Standard1 vCPU · 4 GBEvery plan
Large4 vCPU · 16 GBPro and Power
XL8 vCPU · 16 GBPower
GPURTX 4090 · 4 vCPU · 8 GBPro and Power

GPU boxes run on spare capacity: one can be reclaimed at any time and is deleted when it stops.

Sizes and GPU boxes
A raymarched WebGL2 scene rendering on a GPU box's RTX 4090.

Work that runs while you're away.

Write a job once as a prompt or a script. It runs in your box on a schedule, from a webhook or from your own app, and the box sleeps again when it's done.

The Automations page in the wack dashboard: Nightly build, Visual diff on main and Palette property tests, each succeeded, with templates below.
The Automations page in the wack dashboard: Nightly build, Visual diff on main and Palette property tests, each succeeded, with templates below.

Automations

Claude Code, Codex or a shell script, on a schedule in your time zone, from a webhook or from your app. Results land as files in the box, with an email summary and a link.

  1. 01Approve the app once
  2. 02Its agent starts in your box
  3. 03Your laptop can sleep; the work goes on

Cloud sessions

Desktop apps like monocode can start Claude Code or Codex in your box instead of on your laptop. Close the lid and the session keeps going.

Cloud sessions
An automation's page in the wack dashboard: Nightly build runs cd ~/notes && npm ci && npm run build daily at 2:00, New York time, with its next three runs.

Every run

A run wakes the box, works for up to 60 minutes and lets it sleep again. Agent runs use your own Claude or OpenAI account.

How automations work

A/B test a change on two identical boxes.

Ask your agent whether a branch changes how a page renders. It runs both versions on boxes made from one image, so the only difference between them is your code.

  1. box_image_saveSets up one box with your repo, a pinned Chrome and your fonts, and saves it as an image.
  2. box_createStarts two temporary boxes from that image, each with a screen. They differ in nothing yet.
  3. box_execEach box checks out its revision, starts the dev server and drives a real browser to the same state.
  4. box_deleteCompares the two screenshots pixel by pixel, reports what changed and deletes both boxes.

Your agent reports

14,732 pixels differ (1.44%), over your 0.1% budget. The diff is in qa/diff.png.

A visual diff report in Chrome on a wack box: baseline and candidate renders of a 3D scene, with the 1.44% of pixels that changed marked in orange.
A real report from a box: baseline and candidate rendered on the same Chrome build.

Boxes without a GPU draw WebGL on the CPU, which is slower but very repeatable. For hardware WebGL and WebGPU, compare GPU box to GPU box. Pixel tests

Pay for awake hours. Asleep is free.

Plans are sized in awake hours. Sleeping boxes don't use them, and running out never costs extra.

  • Hobby

    $19 / month

    One box for the agent you already use.

    40 awake hours · 1 box · Standard size

  • Pro

    $49 / month

    Room for agents that work every day.

    150 awake hours · 3 boxes · Large and GPU sizes

  • Power

    $149 / month

    For fleets of agents and heavy automations.

    500 awake hours · 10 boxes · Every size

Every plan starts with a 7-day trial: 10 awake hours, no card.

Compare plans

Common questions.

More answers in the docs
What is a box?

A Linux computer in the cloud that belongs to you. A standard box has 1 vCPU and 4 GB of memory (about 3.8 GB usable), root access and a disk that persists. It comes with the usual tools installed, sleeps when idle and wakes in about a second. How boxes work.

Does wack include the AI model?

No. wack is the computer, not the model. Your agent keeps using your own Claude, ChatGPT or other subscription or API key.

Does my agent keep working after I close my laptop?

Automations and cloud sessions run in the box, so they carry on without your laptop. An agent running on your laptop stops when the laptop sleeps, and the box goes to sleep 10 minutes after its last call. How automations work.

What happens when a box sleeps?

Its disk and memory are kept and it uses none of your awake hours. The next tool call wakes it in about a second, with everything where it was. It never sleeps during a command, an automation run or a cloud session. Large and XL boxes keep their files but restart their programs, and a GPU box ends instead of sleeping.

Can my agent reach my laptop?

No. Your agent sends work to the box, and files move only when it uploads or downloads them. wack never connects to your computer. Security.

What if I use up my awake hours?

Nothing is billed extra. Running work finishes, and boxes can't wake again until your hours reset at the start of your next billing period or you upgrade. See the limits.

Which agents can connect?

Claude Code, Codex, Cursor, Claude (desktop, web and mobile), VS Code, Gemini CLI, Windsurf and any other client that supports remote MCP servers. Steps for each client.

Give your agent a box.

Your first box is ready about 20 seconds after you sign up. 7 days free, no card.

Get your boxRead the docs