runlease

Guide · Claude Code

A sandbox for Claude Code, on a machine that is not yours to lose

Claude Code is most useful when it can run things: install the dependencies, start the stack, run the tests, try again. Runlease gives it a separate Linux machine for that, in your own cloud account, and takes the machine away when the lease ends.

Why a separate machine

An agent that runs commands on your laptop runs them next to your SSH keys, your cloud credentials and every other project you have checked out. A container on the same laptop narrows that, but it still shares your kernel, your network and your battery.

A leased machine is a different computer. Generated code, an install script from a repository you have not read, or a test suite that needs sixteen cores runs there. Your keys stay on your machine: Runlease does not copy them to the VM, and the relay between you and the VM cannot read the session.

ISOLATED

Not your laptop

A real VM in your cloud account, with no public address by default.

CHEAP

Spot prices

You pay your cloud directly. The price is shown before launch.

TEMPORARY

It deletes itself

Two hours by default, whether or not the session that asked for it is still alive.

Set it up

Install the CLI, sign in to the free relay, and prove one launch by hand. Claude uses the same sign-ins you do.

$ curl -fsSL https://runlease.online/install.sh | sh
$ runlease login                 # the free public relay: approve a short code in a browser
$ runlease doctor                # checks sign-ins, project and network, prints the fix
$ runlease up -p gcp -n box -d   # or -p aws
$ runlease down box --yes

Then add the plugin, at the prompt of a Claude Code session:

/plugin install runlease --marketplace marshal-org/runlease

If you only want the typed tools and not the skills, register the MCP server instead: claude mcp add runlease -- runlease mcp. More on the MCP server.

What Claude does with it

The plugin adds skills that Claude reads when the task fits. You do not call them.

SkillWhen Claude uses it
runlease:machineA task needs a separate machine: a long build, more cores, a clean Linux box, a port to preview
runlease:sandboxCode that should not run on your computer: generated code, an unfamiliar repository, an install script
runlease:fanoutA job that splits across several machines: test shards, a version matrix
runlease:setup, runlease:troubleshootSomething is not installed or signed in, a command fails, or machines may have been left running

A typical sandbox run is three commands, which Claude issues as typed tool calls:

$ runlease up -n sandbox --ttl 1h -d
$ runlease push sandbox ./run.sh /tmp/run.sh
$ runlease exec sandbox -- bash /tmp/run.sh

What you see while it works

The plugin draws in the Claude Code window itself. Type /runlease for the machines pane. Each machine has its cloud, region and size, the time left on its lease as a bar that drains, its hourly rate and what it has cost so far.

Runlease                                         1 machine · $0.15/h
────────────────────────────────────────────────────────────────────
● box ▾                                                     41m left
  gcp · europe-west1-b · e2-standard-8
  ━━━━━━━━━━━━━━━━────────  $0.15/h · $0.05 so far
  Lease  +30m  +1h  +4h
  Use in prompt  Copy ssh  Delete
────────────────────────────────────────────────────────────────────
Refresh  Launch another  Docs
Each machine deletes itself when its lease ends.

Open a row to add 30 minutes, 1 hour or 4 hours to the lease, copy its ssh command, start a prompt about the machine, or delete it. Delete takes two presses.

When a lease has under ten minutes left, a band appears above the prompt, with a toast and a desktop notification:

● box 7m left, then it deletes itself   +30m  +1h  Dismiss

The status line carries the same at a glance:

2 machines · box 7m left · $0.15/h

The view reads the list of machines kept on your computer every 30 seconds. It makes no cloud call, and nothing is extended or deleted unless you press a button. The pane, the warning time and the notification are settings under /config.

What it will not do

Questions

Does Claude Code itself run on the VM?

No. Claude Code stays on your computer and sends commands to the machine, the way you would with ssh. Your conversation and your credentials do not move.

Can the code on the VM use sudo?

Not by default. Software a job needs is installed by the manifest's setup steps at boot, or you turn on sudo: passwordless in the manifest when you want the machine to be freely changeable.

What if the session crashes with a machine running?

The lease still ends. The timer is on the VM, not in the session, so the machine deletes itself on time with nothing watching it.

How many machines can it launch?

Two at once on the free public relay. Run your own relay to set your own limit.

Running agents for a whole team? Runlease gives one agent one machine. Marshal, from the same team, runs AI coding agents in isolated pods inside your own VPC, with credential isolation, audited egress and live tool policies.

More guides