Quickstart

wack gives the agent you already use its own cloud computer, called a box. It is a persistent Linux machine with the usual tools already installed. It sleeps when idle, wakes in about a second, and keeps its files.

1. Get your box

Sign up at https://wack.sh. Your 7-day trial starts right away, with no card. It includes 10 awake hours on the Hobby plan.

Your first box, called "my box", is set up in the background. Get set up on Boxes shows Box ready once it's done, usually within about 20 seconds.

2. Connect your agent

Click Connect agent under Get set up on Boxes (or + next to Connect an agent in the sidebar) and pick your agent: Claude Code, Codex, Cursor, Claude, VS Code or any other MCP client. Copy the one command, config or link it shows. For Claude Code that's:

claude mcp add --transport http --scope user wack https://api.wack.sh/mcp/wac_…

The page waits for your agent and turns to Connected by itself. Your agent gets all your boxes, and can make new ones when a job needs more than one. Connect has the exact steps for each client, and how to connect an agent to just one box.

The URL at the end is a secret: anyone who has it can use your boxes. Keep it out of shared repos and screenshots. If it leaks, rotate it under Settings › Connection.

3. Give it a job

Ask for something that needs a real computer. For example:

• "Turn this CSV into a chart and a one-page PDF report."
• "Take screenshots of our pricing page on mobile and desktop."
• "Clone my repo, run the tests and summarize the failures."

The box keeps what your agent makes. Deliverables go to /mnt/user-data/outputs, and you can download them from the box's Files tab in the dashboard.

4. Let it work while you're away

Your box keeps its files while you're away, but it sleeps 10 minutes after your agent's last call, and anything left running in it pauses until it wakes. To have work happen without you, create an automation: a prompt or a script that runs on a schedule or from a webhook, then emails you a summary with a link to the files.

The quickest way in is one of the templates on the Automations page, such as Daily digest.

Where to go next

• Boxes: what's installed, how sleep works and where files go.
• Sizes and GPU boxes: bigger machines for builds and dev servers, and a GPU when the job needs one.
• Screen: watch your agent drive a real browser, and take control when you need to.
• Setups and images: the same Chrome version, repos and fonts in every box.
• Limits: what each plan includes and what happens when you reach a limit.