cp base my-feature

A Linux VM you develop in—no laptop setup. Build your tools into a base box once, then cp a ready-to-code clone for every branch, task, and agent in under a second.

# build your base box once: tools, runtimes, dotfiles
$ ssh exe.dev new base --image exeuntu
$ ssh base.exe.xyz 'mise use -g node@22 go@1.24 && nvim +PaqInstall +qa'

# now fork it for each thing you're working on
$ ssh exe.dev cp base my-feature
vm my-feature ready in 0.4s   # copy-on-write, not a rebuild
$ ssh my-feature.exe.xyz

# the default github integration is already there
$ ssh my-feature.exe.xyz \
      'git clone https://github.int.exe.xyz/you/app.git'
# no PAT on the box, no token in your shell history.

# it's just SSH, so your editor already knows how
$ code --remote ssh-remote+my-feature.exe.xyz /root/app
$ cursor --remote ssh-remote+my-feature.exe.xyz /root/app

# or live in it over a plain terminal
$ ssh my-feature.exe.xyz

Start free How cp works

GITHUB — a real app, not a stray token

# inside the devbox — no PAT, no secret in the env
$ git clone https://repo.int.exe.xyz/you/app.git
$ cd app && git switch -c fix-123
$ git push -u origin fix-123

# the gh CLI works too
$ export GH_HOST=repo.int.exe.xyz
$ gh pr create --fill
https://github.com/you/app/pull/1421

GitHub, wired in.

A full GitHub App, not a token on the box. Link your account once; the in-VM proxy authenticates git and gh. Tag-scoped, so every cp clone inherits it.

OAuth, handled. No token rotation.
Off the box. Credentials stay at the proxy.
Clone-safe. cp brings it along.
gh-friendly. Set GH_HOST and go.

See the GitHub integration docs.

Secrets that never touch the box.

GitHub is one of many. Any integration installs an in-VM proxy that adds the auth header on the way out—so your code calls Stripe, OpenAI, or any API with no key on disk, in your env, or in your shell history.

Header auth. Stripe, OpenAI, anything with a bearer token.
Rotate once. Change the key centrally, not on every box.
Tag-scoped. Attach to a tag; every cp clone inherits it.

Read why secrets belong in your HTTP proxy.

INSIDE THE BOX — no key in sight

# call Stripe with no credentials...
$ curl https://stripe.int.exe.xyz/v1/charges -d amount=500
{"id": "ch_3Qx…", "object": "charge", …}

# ...the proxy adds Authorization on the way out.
# the sk_live_… key is never on the box.

A real machine, not a tab in someone’s cloud.

Define it once

Bake tools into a base box, then cp it forever.

Bring your editor

It’s just SSH—VS Code, Cursor, Zed, JetBrains, or a terminal.

Live preview

A real name.exe.xyz hostname with TLS, private by default.

Auto-stop

Idle boxes stop to disk-only and resume in seconds, right where you left off.

Real VMs

KVM-isolated, with root, systemd, and your own kernel.

Instant clones

Copy-on-write cp forks a 40 GB box in under a second.

One devbox per agent.

An agent on your laptop is a risk: it has your data, runs untrusted input, and can reach the internet. Give each run its own fork instead—blast radius is one box. cp to start, rm when it’s done.

Contained. A rogue agent can’t reach your laptop or other work.
Parallel. A box per task, all at once.
Disposable. Throw it away; the base is untouched.

Built for autonomous agents? See agent box.

AGENTS — a fork each

# give three agents three boxes, all from one base
$ for task in auth billing search; do
    ssh exe.dev cp base agent-$task
  done
vm agent-auth ready in 0.4s
vm agent-billing ready in 0.4s
vm agent-search ready in 0.4s
# each agent gets a clean, fully-tooled checkout.

cp base and start coding
in less than a second.

Start free Pricing Docs