DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run coding agents on a remote machine over SSH with Orca

Use Orca's SSH worktrees to run agents, terminals, and file edits on a larger remote box.

Credentials. The remote machine needs SSH access, so keep keys and host credentials out of prompts and out of shared repo files.

Who it is forA developer whose local machine is too small or slow for heavy agent work and who has access to a bigger remote server.

The problemLong agent runs and builds slow down a laptop, and moving work between the laptop and a server by hand is tedious.

The outcomeAgents, git operations, and terminals run on the remote box while you edit files and watch progress from Orca on your desktop.

What you need first

  • A desktop computer running macOS, Windows, or Linux
  • A git repository to work in
  • At least one CLI coding agent (such as Claude Code, Codex, or OpenCode) that you already have access to with your own subscription

Steps

  1. Install Orca with brew install --cask stablyai/orca/orca on macOS, or download a build from https://onorca.dev/download for your system.
  2. Confirm you can already connect to the remote machine over SSH.
  3. Add the remote machine as an SSH worktree in Orca using the SSH docs at https://www.onorca.dev/docs/ssh.
  4. Start an agent in the remote worktree.
  5. Check progress, edit files, and run git commands from Orca while the agent works.

Prompt for your agent

In the stablyai/orca repo, create an SSH worktree on <remote-host> and start an agent there with the task <task-file>. Output the agent's final summary and the list of changed files. Verify that the changed files exist on the remote host and not on the local machine.

Caveat. Orca's SSH worktree setup depends on the remote machine being reachable over SSH, which you must already have working.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page