Guide
Claude Code runs wherever its terminal runs. Move it off your laptop and long tasks survive a closed lid, several sessions stop fighting over one machine, and you can check in from any device. Here are the three common setups and what each one costs you.
Get startedA cloud VM or a spare box at home. Install Node.js, git and Claude Code, and sign in.
Give the server its own deploy key or token rather than copying your personal SSH key onto it.
Run tmux new -s claude, then claude. Detach with Ctrl-b d and the session keeps running after you disconnect. Reattach later with tmux attach -t claude.
This is the cheapest and most flexible option, and all of the upkeep is yours: patching the server, keeping its credentials scoped, and opening a tunnel or port whenever you want to see the app it is building.
If your repository has a dev container definition, your editor can build it on a remote machine and attach to it. Claude Code then runs inside the container, which keeps it apart from the host’s other files. You still own the host, and a container shares the host’s kernel, so it is a weaker boundary than a separate virtual machine.
A hosted workspace gives you the machine without the upkeep. In YOLO Studio, each workspace is a Linux sandbox in its own virtual machine with Claude Code pre-installed. You open it from any browser, connect your Claude subscription or an API key once, and start Claude Code in a tile.
Because there is no machine of yours to protect, Claude Code there runs without permission prompts, and each extra session gets its own lane: a separate git clone on its own branch. Your running app shows in a preview tile beside it, with no tunnel to set up.
| Your own server | Hosted workspace | |
|---|---|---|
| Setup | Provision, install and secure it yourself | Sign in and create a workspace |
| Upkeep | Yours: updates, keys, disk, uptime | None |
| Several sessions at once | Worktrees and tmux windows by hand | One lane per session, created for you |
| Seeing the app | A tunnel or an open port | A preview tile next to the agent |
| Full control of the machine | Yes | Within the sandbox |
On a server, only inside tmux or screen; a plain SSH session ends when the connection drops. In a YOLO Studio workspace, closing the browser tab or the agent’s tile does not stop the agent.
Yes. On your own server you sign in to Claude Code there. In YOLO Studio you connect the subscription once from Agent access, and each session receives a short-lived access token.
Sign in with GitHub, open a workspace on your repository, and put your first agent to work in a few minutes.
Get started
