--- title: "Run Paradev (formerly Superset) agents on a remote host" description: "Add an exe.dev VM to Paradev, formerly Superset, as a remote host over SSH: Claude Code and Codex run there in parallel worktrees, with no API keys." url: https://exe.dev/deploy/paradev category: "AI agents" updated: 2026-10-31 --- # Run Paradev (formerly Superset) agents on a remote host An always-on remote host for Paradev's parallel coding agents. - **Software:** Paradev (https://paradev.com) - **Source:** https://github.com/paradevai/paradev - **License:** Elastic License 2.0 - **Time:** 10 minutes - **Example VM name:** `my-paradev` (yours will differ; on the VM, `hostname` prints it) - **Machine-readable:** https://exe.dev/deploy/paradev/manifest.json ## What you get - Claude Code and Codex on the VM using exe.dev's LLM integration, with no API key to paste - Git set up, with a project at `~/project` for Paradev's worktrees - The VM ready for `superset hosts add`, which installs and signs in Paradev's host service from your computer Running on the VM: - **Paradev desktop app**: on your computer (macOS; Linux AppImage experimental); adds the VM over SSH - **Paradev host service**: `superset start` as the systemd user service superset-host, installed by `superset hosts add`; reaches your devices through Paradev's relay, data in `~/superset, ~/.superset` - **Claude Code and Codex**: preinstalled; connected to exe.dev's LLM integration, data in `~/.claude, ~/.codex` - **Your project and its worktrees**, data in `~/project, ~/.superset/worktrees` How it is reached: - ssh my-paradev.exe.xyz (private): how `superset hosts add` installs the host, and your terminal - Paradev relay (private): how the desktop and iPhone apps reach the host, signed in to your Paradev organization; outbound from the VM ## Deploy with Shelley Open https://exe.dev/new?prompt=Set%20up%20Paradev%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Fparadev.md%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-paradev.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-paradev.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20Claude%20Code%20and%20Codex%20on%20the%20VM%20using%20exe.dev%27s%20LLM%20integration%2C%20with%20no%20API%20key%20to%20paste%0A-%20Git%20set%20up%2C%20with%20a%20project%20at%20%60~%2Fproject%60%20for%20Paradev%27s%20worktrees%0A-%20The%20VM%20ready%20for%20%60superset%20hosts%20add%60%2C%20which%20installs%20and%20signs%20in%20Paradev%27s%20host%20service%20from%20your%20computer%0A%0ARun%20the%20VM-side%20commands%20in%20%22Set%20up%20the%20VM%22%20only%3B%20skip%20creating%20the%20VM.%0AIf%20%60exeuntu%20configure%60%20reports%20an%20existing%20user%20config%2C%20leave%20it%20alone.%0AFor%20%60git%20config%60%2C%20use%20the%20owner%27s%20name%20and%20email%20if%20you%20know%20them%2C%20and%0Askip%20those%20two%20lines%20if%20you%20don%27t.%20If%20%60~%2Fproject%60%20already%20exists%2C%20leave%0Ait%20alone.%20Don%27t%20install%20or%20sign%20in%20to%20Paradev%20on%20the%20VM%3A%20it%20needs%20the%0Aowner%27s%20Paradev%20account%2C%20and%20%60superset%20hosts%20add%60%20on%20their%20computer%20does%0Ait.%20Verify%20with%20the%20checks%20at%20the%20end%20of%20that%20section%3A%20both%20print%20%60OK%60.%0ASkip%20the%20later%20sections%20and%20the%20FAQ.%20Finish%20by%20telling%20the%20owner%20to%20open%0AParadev%20on%20their%20computer%2C%20go%20to%20Settings%20%E2%86%92%20Hosts%20%E2%86%92%20%22Set%20up%20a%20host%20over%0ASSH%22%20and%20enter%20%60exedev%40%3Cthis%20VM%27s%20name%3E.exe.xyz%60%20%28%22Add%20it%20as%20a%20host%22%29%2C%0Aand%20that%20remote%20hosts%20need%20Paradev%27s%20Pro%20plan.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A to create a VM whose agent, Shelley, follows this recipe. From a terminal: ```sh curl -fsSL https://exe.dev/deploy/paradev/prompt.txt | ssh exe.dev new --prompt=/dev/stdin ``` Or follow the steps below by hand. [Paradev](https://paradev.com), formerly Superset, is a desktop app for running many coding agents at once: Claude Code, Codex, OpenCode and other CLI agents, each in its own Git worktree and terminal, with a diff viewer and pull requests beside them. Its remote hosts move that work to another machine. Make the host an exe.dev VM and you get as many CPUs as your plan allows, worktrees on a disk that persists, and agents that keep going when your laptop sleeps. Plain SSH is all `superset hosts add` needs, and every exe.dev VM has it. Claude Code and Codex come preinstalled and use exe.dev's [LLM integration](/docs/integrations-llm): no API keys on the VM, and model usage billed to your exe.dev account. Remote hosts need a Paradev account on the Pro plan. ## 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: ```bash 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: ```bash 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: ```bash 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](https://paradev.com) or its [releases](https://github.com/paradevai/paradev/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](https://docs.paradev.com/cli/getting-started) signed in on your computer: ```bash 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: ```bash 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): ```bash ~/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](/docs/billing/personal) capacity: ```bash 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](/docs/integrations-github) 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: ```bash 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: ```bash 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](/docs/proxy) serves ports 3000 to 9999 behind your exe.dev login until you [share them](/docs/sharing). ## 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: ```bash 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**: ```bash 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](#room-for-more-agents). For everything else, see Paradev's [Remote Access](https://docs.paradev.com/remote-access) and [Host Server](https://docs.paradev.com/cli/host-server) docs. ## Frequently asked questions ### Is Paradev the same as Superset? Yes. Superset renamed itself Paradev on October 26, 2026. The CLI is still called `superset` (`paradev` is an alias), and its files are still `~/superset` and `~/.superset`. It has nothing to do with Apache Superset, the BI tool. ### Do I need a Paradev account? Yes. Hosts register with your Paradev organization, and your devices reach them through Paradev's relay. Remote access is part of the Pro plan ($20 per user per month, or $16 billed yearly, on [Paradev's pricing page](https://paradev.com/pricing) as of October 2026); Free covers local workspaces only. ### Does the Paradev app run on the VM? No. The desktop app stays on your computer. The VM runs Paradev's host service, which owns the worktrees, terminals and agents. It listens only on `127.0.0.1` and connects out to Paradev's relay, so nothing on the VM is open to the internet. ### Do agents keep running when my laptop sleeps? Yes. They run on the VM, which stays on. Paradev keeps terminals in a separate daemon, so they survive a restart of the host service, and the service comes back after a VM reboot. Agents that were running when the VM rebooted need a new start. ### Can I use my own Claude or ChatGPT subscription? Yes. On the VM, run `claude auth login` or `codex login`, after removing what `exeuntu configure` added: `apiKeyHelper` and `env.ANTHROPIC_BASE_URL` in `~/.claude/settings.json`, and the `exe-llm` provider in `~/.codex/config.toml`. Keep the `hooks` entries Paradev added. ### Does the iPhone app work with this? Paradev's iPhone and iPad app reaches hosts through the same relay: sign in with the same account and organization, pick the VM, and open a workspace. Mobile is part of the Pro plan too. ### How much does it cost? The Paradev plan, plus the VM as part of your exe.dev plan. Model usage through the [LLM integration](/docs/integrations-llm) is billed to your exe.dev account; exe.dev keeps a [list of models and prices](/llm-gateway-models). ## Related - [Run Orca's agents on a remote server](https://exe.dev/deploy/orca.md): A big, always-on box for Orca's parallel coding agents. - [Run Herdr agents on a remote machine](https://exe.dev/deploy/herdr.md): An always-on SSH machine for Herdr, with agents ready and no API keys. - [Run T3 Code on a remote server](https://exe.dev/deploy/t3code.md): Your coding agents on an always-on VM, steered from your phone. - [Run Claude Code on a remote server](https://exe.dev/deploy/claude-code.md): A computer for Claude. A breather for your laptop. - [Run Codex on a remote server](https://exe.dev/deploy/codex.md): A computer for Codex. An early night for your laptop. - [Host OpenClaw](https://exe.dev/deploy/openclaw.md): An AI sidekick with its own computer. Your laptop can take a nap.