Documentation

Backends & agents

The bridge serves one kind of terminal at a time, its backend: Herdr, Orca, or plain shells it runs itself. Choose with --backend herdr|orca|plain; the choice is saved, and the console can change it.

Herdr (default)

Herdr is a terminal workspace manager for coding agents. With this backend, Herdr owns the workspaces, tabs, panes and agent sessions; the bridge shows them to your phone and passes your input through. Watching uses a read-only helper, so it never takes over the desktop’s view.

Terminal
herdr-remote up                                  # finds herdr on the PATHherdr-remote up --herdr "$(which herdr)"         # or say where it isherdr-remote serve --session work                # pick a Herdr session (default: the main one)

The easiest setup is to run the bridge in a Herdr tab. Pairing codes also appear as Herdr notifications. Terminal history reaches back up to Herdr’s 1,000 most recent lines; agent conversations go further (see below).

Orca

The bridge can attach to a local Orca runtime instead. Orca’s own runtime access link stays in a private file on the computer; the phone pairs with the bridge’s usual invitation. Use a separate state directory and port if you also run a Herdr bridge.

Terminal
herdr-remote init --backend orca --orca-connection ~/private/orca-access.txt \  --url https://192.168.1.20:8444 --listen 0.0.0.0 --port 8444 --state ~/.local/share/herdr-remote-orcaherdr-remote serve --state ~/.local/share/herdr-remote-orca
  • Orca’s desktop and its own clients can still type into the same terminal; control leases coordinate only the phones paired with the bridge.
  • Import repository registers an existing local Git repository. Starting an agent inside an existing pane is not available; start it from Orca or by typing the command.

Plain terminals

No Herdr or Orca? The bridge runs its own login shells, as you:

Terminal
herdr-remote up --backend plainherdr-remote up --backend plain --folder ~/code/api --folder ~/code/web
  • Each folder becomes a workspace with one shell (your home folder if you give none). Add more from the phone with New workspace; they are remembered for the next start.
  • The terminals themselves end when the bridge stops.
  • One device controls a terminal at a time, and the terminal’s size follows it. History keeps 500, 1,000 or 2,000 lines.
  • Agents you start in these shells are recognised and shown as agents.

Agents

The bridge recognises an agent from the program running in a pane, and offers the ones installed on the computer under Start an agent. For agents marked below, the app reads the agent’s own session log to show its conversation, paged back to the start; for the others it shows the terminal output and says why.

  • Claude Code
    Command: claude
    Conversation history: Yes
  • Codex
    Command: codex
    Conversation history: Yes
  • OpenCode
    Command: opencode
    Conversation history: Terminal output
  • Pi
    Command: pi
    Conversation history: Yes
  • Gemini CLI
    Command: gemini
    Conversation history: Terminal output
  • Qwen Code
    Command: qwen
    Conversation history: Yes
  • Kimi Code
    Command: kimi
    Conversation history: Terminal output
  • GitHub Copilot CLI
    Command: copilot
    Conversation history: Terminal output
  • Cursor CLI
    Command: cursor-agent
    Conversation history: Terminal output
  • Droid
    Command: droid
    Conversation history: Terminal output
  • Amp
    Command: amp
    Conversation history: Terminal output
  • Kiro CLI
    Command: kiro-cli
    Conversation history: Terminal output
  • Cline
    Command: cline
    Conversation history: Terminal output
  • Kilo Code
    Command: kilo
    Conversation history: Terminal output
  • Qoder CLI
    Command: qodercli
    Conversation history: Terminal output
  • Devin CLI
    Command: devin
    Conversation history: Terminal output
  • Antigravity CLI
    Command: agy
    Conversation history: Terminal output
  • Grok CLI
    Command: grok
    Conversation history: Terminal output
  • Hermes Agent
    Command: hermes
    Conversation history: Terminal output
  • Oh My Pi
    Command: omp
    Conversation history: Terminal output
  • Mastra Code
    Command: mastracode
    Conversation history: Terminal output
  • Letta Code
    Command: letta
    Conversation history: Terminal output
  • Maki
    Command: maki
    Conversation history: Terminal output
  • Muse
    Command: muse
    Conversation history: Terminal output
  • Crush
    Command: crush
    Conversation history: Terminal output
  • Goose
    Command: goose
    Conversation history: Terminal output
  • Aider
    Command: aider
    Conversation history: Terminal output
  • Auggie
    Command: auggie
    Conversation history: Terminal output
  • CodeBuddy
    Command: codebuddy
    Conversation history: Terminal output
  • ZCode (Z.ai)
    Command: zcode
    Conversation history: Terminal output
  • DeepSeek Harness
    Command: dsh
    Conversation history: Terminal output

Agents keep running on your computer with your own accounts, settings and model providers; any usage charges are between you and them. The app doesn’t sign in to anything and never approves an agent’s request on its own: a waiting agent shows as Needs input until you answer it.

WhatsApp