Run Paradev (formerly Superset) agents on a remote host

Set up the VM#

On your computer, create a VM and connect once, which also saves its host key. Pick any free name; if you've already clicked Deploy or have a VM, skip the first command and use its name:

ssh exe.dev new --name=my-paradev
ssh my-paradev.exe.xyz

On the VM, connect Claude Code and Codex to the LLM integration, tell Git who you are, and make a project for Paradev's worktrees, a Git repository with a first commit:

exeuntu configure claude
exeuntu configure codex
git config --global user.name "Your Name"
git config --global user.email you@example.com
git init ~/project
git -C ~/project commit --allow-empty -m "Start"

Important

Do this before adding the host. Paradev adds its own hooks to ~/.claude and ~/.codex, and exeuntu configure leaves an existing config alone.

Check that both agents answer through exe.dev:

claude -p "Reply with exactly: OK"
cd ~/project && codex exec "Reply with exactly: OK"

Add it as a host#

On your computer, install Paradev from paradev.com or its releases and sign in. Then open Settings → Hosts, choose Set up a host over SSH, and enter:

exedev@my-paradev.exe.xyz

The app uses your computer's ssh, so the key you use for exe.dev works as it is. Answer Yes when it asks to install the Paradev CLI. The same thing from a terminal, with Paradev's CLI signed in on your computer:

superset hosts add exedev@my-paradev.exe.xyz

hosts add does everything on the VM for you:

• installs the Paradev CLI into ~/superset (about 270 MB; the command is still superset, with paradev as an alias);
• creates an API key in your Paradev account, named after the host, and signs the VM in with it, sent over SSH rather than typed;
• runs the host service as the systemd user unit superset-host, which exe.dev VMs start at boot with no login needed (lingering is already on);
• waits until the host is online on Paradev's relay.

The VM now shows up in Settings → Hosts as my-paradev, and in the Device filter of the Workspaces list. To check from the VM:

systemctl --user status superset-host
~/superset/bin/superset status

Run agents on it#

On the VM, register ~/project with Paradev on this host (the CLI is already signed in):

~/superset/bin/superset projects create --name project --local --import ~/project

In the app, create a workspace in project with my-paradev as the host, pick Claude or Codex, and give it a task, such as:

Write index.html: a one-page site for a very opinionated cat. Keep it short.

The agent runs on the VM, in a new branch and worktree under ~/.superset/worktrees/. Create more workspaces for more agents; each one gets its own branch, and the sidebar shows which agent is working, done, or waiting on you.

Paradev starts agents with their permission prompts off (Claude Code's --dangerously-skip-permissions, Codex's --dangerously-bypass-approvals-and-sandbox), which suits a VM that holds nothing else; a worktree is a separate checkout, not a sandbox.

Warning

Anyone who can open a workspace on the host can run any command on the VM as exedev. A new host is yours alone; add teammates under Settings → Hosts only if you'd give them a shell.

Room for more agents#

A new VM has 2 vCPUs, 8 GB of memory and a 25 GB disk, enough for a few agents. Builds, tests and dev servers in many worktrees at once need more. On your computer, give the VM more, up to your plan's capacity:

ssh exe.dev resize my-paradev --cpu=8 --memory=32GB --disk=100GB

Disks can only grow. Each worktree is a full checkout with its own dependencies, so check df -h / on the VM now and then, and delete workspaces you've merged.

Bring your code#

Connect a GitHub repo to the VM and it can clone, pull and push without a token or deploy key on it. On your computer, replace you/app with your repository:

ssh exe.dev integrations add github --name app --repository you/app --attach vm:my-paradev

On the VM, clone it and register it with Paradev:

git clone https://github.int.exe.xyz/you/app.git ~/app
~/superset/bin/superset projects create --name app --local --import ~/app

Workspace branches push through the integration. Paradev's pull request and checks panes, and its clone dialog, work through gh on the host and expect a github.com remote. For those, run gh auth login on the VM and clone from github.com instead; that keeps a GitHub token on the VM.

Preview what they build#

When you open a workspace on the VM, the desktop app forwards the ports that workspace's dev servers listen on to the same port on your computer, so localhost:3000 reaches the VM. To look from anywhere else, ask the agent to listen on 0.0.0.0 and open https://my-paradev.exe.xyz:3000/: exe.dev's HTTPS proxy serves ports 3000 to 9999 behind your exe.dev login until you share them.

Back up, update and remove#

Commit and push your work from each workspace; that's the copy that matters. For a copy of the whole VM, run this on your computer:

ssh exe.dev cp my-paradev my-paradev-backup

The copy gets its own machine ID, so if its host service starts it registers as a second host, signed in with the same key. Unless you mean to switch to it, run systemctl --user disable --now superset-host on the copy.

To update the host, run Set up a host over SSH (or superset hosts add) again after Paradev updates on your computer: it brings the VM's CLI to the same version, restarts the service, and leaves the rest alone. Update the agents with sudo exeuntu update claude and sudo exeuntu update codex.

To stop using the VM as a host, run this on your computer. It stops and removes the service and revokes the API key; then delete the host in Settings → Hosts:

superset hosts remove exedev@my-paradev.exe.xyz

Troubleshooting#

• Set up fails to connect. Check that ssh exedev@my-paradev.exe.xyz true works in a terminal on your computer, with the same key.
• The host is offline. On the VM, read the service's log with journalctl --user -u superset-host -n 50. Not logged in means the API key is gone or revoked; run Set up a host over SSH again.
• An agent asks for a login or API key. The host was added before exeuntu configure ran. On the VM, move ~/.claude/settings.json and ~/.codex/config.toml aside, run exeuntu configure claude and exeuntu configure codex, then systemctl --user restart superset-host so Paradev adds its hooks again.
• The VM is slow with many agents. Check uptime and free -h on the VM, then give it more.

For everything else, see Paradev's Remote Access and Host Server docs.