{ "manifest_version": "1", "slug": "paradev", "title": "Paradev", "headline": "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.", "category": "ai-agents", "tags": [ "paradev", "superset", "superset.sh", "superset hosts add", "remote host", "parallel agents", "git worktrees", "claude code", "codex" ], "url": "https://exe.dev/deploy/paradev", "markdown_url": "https://exe.dev/deploy/paradev.md", "upstream": { "website": "https://paradev.com", "source": "https://github.com/paradevai/paradev", "docs": "https://docs.paradev.com/remote-access", "license": "Elastic License 2.0" }, "example_vm_name": "my-paradev", "time": "10 minutes", "stack": [ { "name": "Paradev desktop app", "detail": "on your computer (macOS; Linux AppImage experimental); adds the VM over SSH" }, { "name": "Paradev host service", "detail": "`superset start` as the systemd user service superset-host, installed by `superset hosts add`; reaches your devices through Paradev's relay", "data": "~/superset, ~/.superset" }, { "name": "Claude Code and Codex", "detail": "preinstalled; connected to exe.dev's LLM integration", "data": "~/.claude, ~/.codex" }, { "name": "Your project and its worktrees", "data": "~/project, ~/.superset/worktrees" } ], "access": [ { "url": "ssh my-paradev.exe.xyz", "who": "private", "what": "how `superset hosts add` installs the host, and your terminal" }, { "url": "Paradev relay", "who": "private", "what": "how the desktop and iPhone apps reach the host, signed in to your Paradev organization; outbound from the VM" } ], "delivers": [ "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" ], "deployable": true, "deploy": { "new_vm_url": "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", "terminal": "curl -fsSL https://exe.dev/deploy/paradev/prompt.txt | ssh exe.dev new --prompt=/dev/stdin", "prompt": "Set up Paradev on this VM by following the exe.dev recipe at https://exe.dev/deploy/paradev.md from top to bottom.\n\nThe recipe's example VM name is my-paradev. This VM's name is the output of `hostname`: use it wherever the recipe writes my-paradev. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- Claude Code and Codex on the VM using exe.dev's LLM integration, with no API key to paste\n- Git set up, with a project at `~/project` for Paradev's worktrees\n- The VM ready for `superset hosts add`, which installs and signs in Paradev's host service from your computer\n\nRun the VM-side commands in \"Set up the VM\" only; skip creating the VM.\nIf `exeuntu configure` reports an existing user config, leave it alone.\nFor `git config`, use the owner's name and email if you know them, and\nskip those two lines if you don't. If `~/project` already exists, leave\nit alone. Don't install or sign in to Paradev on the VM: it needs the\nowner's Paradev account, and `superset hosts add` on their computer does\nit. Verify with the checks at the end of that section: both print `OK`.\nSkip the later sections and the FAQ. Finish by telling the owner to open\nParadev on their computer, go to Settings → Hosts → \"Set up a host over\nSSH\" and enter `exedev@\u003cthis VM's name\u003e.exe.xyz` (\"Add it as a host\"),\nand that remote hosts need Paradev's Pro plan.\n\nFinish with the URLs I should open.\n", "prompt_url": "https://exe.dev/deploy/paradev/prompt.txt" }, "updated": "2026-10-31", "related": [ "orca", "herdr", "t3code", "claude-code", "codex", "openclaw" ], "alternatives": [ "Conductor", "Codex app" ] }