{
  "manifest_version": "1",
  "slug": "orca",
  "title": "Orca",
  "headline": "Run Orca's agents on a remote server",
  "description": "Make an exe.dev VM the remote box for Orca's SSH worktrees: Claude Code and Codex run there in parallel, with no API keys, while your laptop sleeps.",
  "category": "ai-agents",
  "tags": [
    "orca",
    "orca ide",
    "ssh worktrees",
    "parallel agents",
    "git worktrees",
    "remote coding agents",
    "claude code",
    "codex"
  ],
  "url": "https://exe.dev/deploy/orca",
  "markdown_url": "https://exe.dev/deploy/orca.md",
  "upstream": {
    "website": "https://www.onorca.dev",
    "source": "https://github.com/stablyai/orca",
    "docs": "https://www.onorca.dev/docs/ssh",
    "license": "MIT"
  },
  "example_vm_name": "my-orca",
  "time": "10 minutes",
  "stack": [
    {
      "name": "Orca desktop app",
      "detail": "on your computer (macOS, Windows or Linux); it drives the VM over SSH"
    },
    {
      "name": "Orca's remote server",
      "detail": "installed by the desktop app on first connect; runs terminals and agents, on localhost:6768 through SSH",
      "data": "~/.orca-remote, ~/.orca"
    },
    {
      "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, ~/orca/workspaces"
    }
  ],
  "access": [
    {
      "url": "ssh my-orca.exe.xyz",
      "who": "private",
      "what": "how Orca on your computer reaches the VM, and your terminal"
    },
    {
      "url": "https://my-orca.exe.xyz/",
      "who": "private",
      "what": "a dev server an agent starts on port 8000, behind exe.dev login"
    }
  ],
  "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 Orca's worktrees",
    "The VM ready to add in Orca as an SSH target; Orca installs its own server on first connect"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe.dev/new?prompt=Set%20up%20Orca%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Forca.md%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-orca.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-orca.%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%20Orca%27s%20worktrees%0A-%20The%20VM%20ready%20to%20add%20in%20Orca%20as%20an%20SSH%20target%3B%20Orca%20installs%20its%20own%20server%20on%20first%20connect%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.%20Verify%20with%20the%20checks%20at%20the%20end%20of%20that%20section%3A%20both%20print%0A%60OK%60.%20Skip%20the%20later%20sections%20and%20the%20FAQ.%20Finish%20by%20telling%20the%20owner%20to%0Aadd%20%60%3Cthis%20VM%27s%20name%3E.exe.xyz%60%20with%20user%20%60exedev%60%20in%20Orca%20under%0ASettings%20%E2%86%92%20SSH%20%28%22Connect%20Orca%22%29%2C%20and%20that%20%60%2Fhome%2Fexedev%2Fproject%60%20is%20the%0Aproject%20to%20add.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe.dev/deploy/orca/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Orca on this VM by following the exe.dev recipe at https://exe.dev/deploy/orca.md from top to bottom.\n\nThe recipe's example VM name is my-orca. This VM's name is the output of `hostname`: use it wherever the recipe writes my-orca. 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 Orca's worktrees\n- The VM ready to add in Orca as an SSH target; Orca installs its own server on first connect\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. Verify with the checks at the end of that section: both print\n`OK`. Skip the later sections and the FAQ. Finish by telling the owner to\nadd `\u003cthis VM's name\u003e.exe.xyz` with user `exedev` in Orca under\nSettings → SSH (\"Connect Orca\"), and that `/home/exedev/project` is the\nproject to add.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe.dev/deploy/orca/prompt.txt"
  },
  "updated": "2026-10-31",
  "verified": "2026-10-31",
  "related": [
    "herdr",
    "t3code",
    "claude-code",
    "codex",
    "code-server",
    "openclaw"
  ]
}