Orca

A desktop ADE for running and reviewing parallel CLI coding agents in isolated Git worktrees.

Source repo
stablyai/orca
Stars
★ 117k
Last updated
today
License
MIT
Primary language
TypeScript

At a glance

How it runs
Desktop appCLI
Works with
Universal · cross-platformCodex · Claude Code
Cost
Free software; you pay for model usage
Setup effort
Medium · a few setup steps
You'll need
GitShell / CLINetwork accessLocal filesystem
Typical use
A developer evaluating several fixes for the same bug can fan one prompt out to multiple agents, compare their isolated worktrees, and merge the preferred result.
Not a fit if
  • Teams without a Git-based workflow who can't use worktree isolation
  • Users who want a browser-only tool and won't install a desktop app

What does this agent do, and when should you use it?

Orca is an agent development environment for coordinating parallel coding agents, with each agent assigned its own Git worktree. It explicitly supports Codex, Claude Code, OpenCode, Pi, and other CLI agents that run in a terminal. The desktop application combines terminal splits, file editing, an embedded Chromium-based Design Mode, GitHub and Linear workflows, and line-level annotations on AI-generated diffs. It is distributed for macOS, Windows, and Linux, with iOS and Android companion apps for status monitoring, notifications, and follow-up messages. For remote development, SSH worktrees run agents on a remote machine with file editing, Git, terminals, automatic reconnection, and port forwarding.

A user sends prompts to one or more CLI coding agents in Orca; the same prompt can be fanned out across agents, each running in an isolated Git worktree. Agents work through terminals, and their output is surfaced as workspace file changes, Git diffs, and changes that can be committed; users can inspect and edit work, annotate individual diff lines, and send that feedback back to an agent. Orca documents CLI workflows including orca worktree create, snapshot, click, and fill. Its Design Mode lets a user select an element in a Chromium window and send that element's HTML, CSS, and a cropped screenshot into an agent prompt. SSH worktrees move the agent, file editing, Git, and terminal activity onto a remote machine.

  1. A developer evaluating several fixes for the same bug can fan one prompt out to multiple agents, compare their isolated worktrees, and merge the preferred result.
  2. An engineer who already uses Codex, Claude Code, OpenCode, or Pi can run those terminal agents side by side in one desktop workspace.
  3. A team with a powerful remote Linux machine can use SSH worktrees for agents while retaining file editing, Git, terminal access, reconnection, and port forwarding.
  4. A reviewer assessing AI-produced changes can attach comments to precise diff lines and send the requested revisions back to the agent.
  5. A developer away from their desk can use the iOS or Android companion app to receive completion notifications and send follow-up instructions.

How do you install or deploy this agent?

Install the documented desktop package for your platform:

macOS: brew install --cask stablyai/orca/orca

Arch Linux: yay -S stably-orca-bin

Desktop builds are explicitly listed for macOS (Apple Silicon and Intel), Windows (.exe), and Linux (AppImage). The mobile companion is available through the iOS App Store/TestFlight or the Android APK listed in the README. You also need a terminal-runnable CLI agent and that agent's own subscription. The supplied evidence does not document complete first-launch, agent-authentication, or mobile-pairing steps.

How do you use this agent?

Open a Git repository in Orca and start a terminal CLI coding agent. To explore alternatives in parallel, send the same prompt to multiple agents so each works in its own Git worktree. Compare the resulting file changes and diffs, add line comments where revisions are needed, send feedback to the agent, then choose a result to merge or commit. Documented CLI workflow names include orca worktree create, orca snapshot, orca click, and orca fill; the supplied material does not include their arguments or a complete runnable workflow example.

What are this agent's strengths and limitations?

Pros
  • Runs parallel agents in separate Git worktrees, allowing alternatives to be compared before a result is merged.
  • Supports multiple terminal-based coding agents instead of one named provider; the README explicitly includes Codex, Claude Code, OpenCode, and Pi.
  • Brings terminal splits, file editing, AI-diff annotations, GitHub/Linear browsing, and Design Mode into one desktop workspace.
  • Provides SSH worktrees with documented automatic reconnection and port forwarding.
  • The mobile companion can notify users when an agent finishes and accept follow-up instructions.
Limitations
  • Its core workflow depends on users having terminal-runnable coding agents installed and their own subscriptions.
  • Parallel isolation is based on Git worktrees, so projects outside a Git-based workflow do not directly receive that model.
  • The supplied material lacks complete setup details for first launch, CLI-agent authentication, SSH configuration, and command arguments for the Orca CLI.
  • GitHub, Linear, SSH, mobile, and Design Mode workflows depend on the relevant services, network access, and platform conditions.

How does this agent compare with similar options?

Compared with using Codex, Claude Code, OpenCode, or Pi directly in a single terminal, Orca is positioned as the workspace that runs, compares, and reviews multiple terminal agents in separate Git worktrees; it does not replace those CLI agents themselves.

Key facts side by side with the most closely related agents.

Agent Source review Form / cost Stars Updated Language Full support on
Orca This agent 50 · Major gaps Desktop appFree + model costs ★ 117k today TypeScript Codex · Claude Code
Ivy Tendril 56 · Major gaps Desktop appFree + model costs ★ 203 1mo ago C# Codex · Claude Code
Superset 52 · Major gaps Desktop appFreemium ★ 16k today TypeScript Codex · Claude Code
Alas Agent Workspace 78 · Good Desktop appFree + model costs ★ 23 today Swift Codex · Claude Code

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Major gaps
50/ 100 5-point scale 2.5 / 5
This review covers the source as of Aug 09, 2026. The project has shipped 34 stable release(s) since, which have not been re-reviewed. The score and verdict describe the reviewed version only. Recent releases ↓
Trust 8/29
Reliability 9/14
Adaptability 12/18
Convention 11/18
Effectiveness 7/13
Verifiability 3/8
Why each dimension lost points
Trust8 / 29 · 1.4/5

Evidence shows: README mentions privacy and telemetry docs but lacks specifics; package.json includes posthog-node telemetry dependency without data flow details; workflow files show careful handling of GitHub tokens and signing credentials but not user data. Deductions: no user confirmation mechanism, insufficient data flow transparency, missing sensitive data handling details, no dependency security audit shown, external effects (e.g., SSH, computer use) lack explicit permission boundaries, rollback not mentioned, source attribution partial (publisher unverified).

Reliability9 / 14 · 3.2/5

Evidence shows: README and package.json are consistent, version number present, extensive test scripts, workflow files include detailed failure handling. Deductions: no dependency availability guarantees (e.g., lockfile, mirrors), failure messages only in CI workflows, not at user interface level.

Adaptability12 / 18 · 3.3/5

Evidence shows: README clearly targets '100x builders' and multiple scenarios (parallel worktrees, mobile companion, SSH), supports many CLI agents, provides multi-platform install instructions. Deductions: capability boundaries not explicit (e.g., computer use permissions), trigger precision (e.g., CLI commands) not detailed, environment fit (e.g., headless Linux) only partially mentioned.

Convention11 / 18 · 3.1/5

Evidence shows: README well-structured, install notes detailed, naming stable (orca), examples and FAQ via docs links, MIT license clear, version number present, maintenance responsibility via contributing guide and community channels. Deductions: known limitations not explicitly listed, changelog not directly provided (only via releases link).

Effectiveness7 / 13 · 2.7/5

Evidence shows: output usability (e.g., CLI commands, mobile app) described, marginal value (parallel agent orchestration) clear, cost-benefit (use own subscription) mentioned. Deductions: cost-benefit not quantified, lack of specific performance data.

Verifiability3 / 8 · 1.9/5

Evidence shows: feature claims in README have doc links but no independent verification; test files exist but no test results shown; facts and inferences not clearly separated. Deductions: claim traceability insufficient, cross-source corroboration lacking, fact-inference separation unclear.

Risks and how to mitigate them
  • Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
  • Publisher identity unverified; treat source with caution.
  • Telemetry data flow opaque; review privacy policy.
  • Dependency security not audited; check for known vulnerabilities.
  • External effects (e.g., SSH, computer use) lack explicit permission boundaries.
Evidence confidence: Low Reviewed Aug 09, 2026 Reviewed revision e172a51649b8 New commits since this review; the score may not cover them
See the full review method →

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

  1. v1.4.250
    Release notes excerpt
    We did two releases today! Be sure to check out the [v1.4.249 release notes](https://github.com/stablyai/orca/releases/tag/v1.4.249), which include easier Chat or Terminal setup, more control over conversations, and a redesigned phone Home. Lower terminal memory use, clearer chat changes & a Chrome-compatible password manager ✨ - ⚡ Lower terminal memory use: Stop repeatedly reading and parsing font files for terminal ligatures, fixing a source of high memory use and launch crashes in sessions with many terminals. …
    View on GitHub ↗
  2. v1.4.249
    Release notes excerpt
    Easier setup, more control over chats & tidier workspaces ✨ - 🎛️ Choose Chat or Terminal from the start: Onboarding now lets you pick Chat UI or Terminal, then choose an agent and install the skills for that setup. - 💬 Keep control of conversations: Preserve chat inputs through uncertain delivery and Stop, choose whether sending moves the scroll position, and decide when idle chat agents stop—or keep them running. - 🗂️ Keep projects tidy: Adding a project keeps discovered worktrees hidden, while create and clone handle symlinked parent folders consistently. …
    View on GitHub ↗
  3. v1.4.248
    Release notes excerpt
    More reliable terminals, dependable chats & easier AI choices ✨ - 🖥️ More reliable terminals: Keep active remote streams connected, preserve agent identity across daemon restarts, improve ordered mobile input and long messages to Windows Codex, and render Nerd Font symbols correctly after fonts load. - 💬 More dependable conversations: Keep streaming replies after their prompts, hold queued follow-ups when a turn fails, and keep pasted text and terminal drafts separate from chat sends. …
    View on GitHub ↗

FAQ

Is Orca tied to one model or agent provider?
No. It states that it works with any CLI agent that runs in a terminal, and explicitly lists Codex, Claude Code, OpenCode, Pi, and others.
Do I need separate subscriptions for coding agents?
Yes, the README says agents can be run with your own subscription. Pricing and authentication depend on the selected agent.
Can it run work on a remote server?
Yes. SSH worktrees are documented for running agents on a remote machine with file editing, Git, terminals, automatic reconnection, and port forwarding.
What survives a restart or disconnection?
The README states that terminal scrollback survives restarts, and SSH worktrees include automatic reconnection.
Is the CLI fully documented in the supplied material?
Only workflow names are provided: orca worktree create, snapshot, click, and fill. Their argument syntax and a complete end-to-end example are not included.
View on GitHub ↗ Install ↓

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related agents