Neil
f1be93c669
I proposed making the pane-retry path request source recovery the way reattachKnownPtys does, and argued it was probably client-side routing. Tracing it says the wiring is indeed trivial and the checkpoint state does survive a drop — and that the change would still be wrong three ways, one of them harmful. The relay short-circuits to 'existing' on a same-clientId attach BEFORE it looks at the recovery argument, and the reconnecting client has already rotated the delivery onto its id. A failed reattachKnownPtys then deletes the checkpoint on purpose, so a later pane retry presents checkpointUnavailable, which becomes restoreRequired and then SSH_SESSION_EXPIRED_ERROR — trading a blank pane with a tail for a killed session. And the payloads answer different questions anyway: recovery replays the post-checkpoint delta to keep main's model whole, while the tail is a screen snapshot for a fresh empty xterm. Even a successful recovery would put almost nothing in a remounted pane. Also corrects the argument I had been leaning on hardest. "Old relays ignore requireReplay, so those users still get blank panes" is false for the SSH relay: the client deploys its own relay into a version-scoped directory and rejects any grant whose serverBuildId differs, because client and relay ship in one build. Mixed versions cannot occur on this channel. The independent-update rule still governs remote runtime hosts, just not this one — so there is no stranded population, and the urgency that framing created was imaginary. What replaces it is a sharper question. Source recovery is gated on outputFlowControl and on the client presenting a NEW clientId. We have empirical evidence it does not: the blank-pane bug existed because the relay concluded this client already held the stream, and the shipped fix works by bypassing that exact early return. If the id is reused, reattachKnownPtys' recovery hits the same short-circuit — meaning checkpointed recovery may never have run for SSH reconnects, and the tail is not a fallback but the only path. Whether that is so turns on daemon versus stdio-primary relay mode, which I did not verify and which decides whether the work is "extend recovery" or "recovery has never run here."
Orca
中文 · 日本語 · 한국어 · Español · Français · Português
The AI Orchestrator for 100x builders.
Run Codex, ClaudeCode, OpenCode or Pi side-by-side — each in its own worktree, tracked in one place.
Download Orca
Features
Mobile CompanionMonitor and steer your agents from your phone — get notified when an agent finishes and send follow-ups from anywhere. |
 |
Parallel WorktreesFan one prompt across five agents, each in its own isolated git worktree — compare the results and merge the winner. |
 |
Terminal SplitsGhostty-class terminals with WebGL rendering, infinite splits, and scrollback that survives restarts. |
 |
Design ModeClick any UI element in a real Chromium window to send its HTML, CSS, and a cropped screenshot straight into your agent's prompt. |
 |
GitHub & Linear, NativeBrowse PRs, issues, and project boards in-app — open a worktree from any task and review without a context switch. |
 |
SSH WorktreesRun agents on a beefy remote box with full file editing, git, and terminals — auto-reconnect and port forwarding included. |
 |
Annotate AI DiffsDrop comments on any diff line and ship them back to the agent — review, edit, and commit without leaving Orca. |
 |
Drag Files to AgentsVS Code's editor with autosave everywhere — drag files or images straight into an agent prompt. |
 |
Orca CLIAgents drive Orca too — script every workflow with |
 |
Also in the box:
- Quick open — Search across worktrees, files, agents, commands, and repo context without leaving your flow.
- Account switcher & usage tracking — See Claude and Codex usage and rate-limit resets, and hot-swap accounts without re-logging in.
- Rich repo previews — Preview Markdown, images, PDFs, and repo docs in the workspace.
- Computer Use — Let agents operate desktop apps and visible UI when a workflow needs real interaction.
- Notifications and unread state — Know when an agent finishes or needs attention, then mark threads unread to come back later.
- And many, many more — we ship daily, so this list is perpetually behind. The changelog is the real feature list.
Supported Agents
Works with any CLI agent — if it runs in a terminal, it runs in Orca.
Claude Code
Codex
Grok
Cursor
GitHub Copilot
OpenCode
MiMo Code
Amp
OpenClaude
Antigravity
Pi
oh-my-pi
Hermes Agent
Devin
Goose
Auggie
Autohand Code
Charm
Cline
Codebuff
Command Code
Continue
Droid
Kilocode
Kimi
Kiro
Mistral Vibe
Qwen Code
Rovo Dev
+ any CLI agent
Install
Desktop — macOS, Windows, Linux
- Download from onOrca.dev
- Or grab a build directly: macOS Apple Silicon · macOS Intel · Windows (.exe) · Linux AppImage · All builds
- Running
orca serveon a headless Linux server? See the headless Linux server guide.
Or via a package manager:
# macOS (Homebrew)
brew install --cask stablyai/orca/orca
# Arch Linux (AUR) — or stably-orca-git to build from source
yay -S stably-orca-bin
Mobile Companion — iOS, Android
Pair with your desktop app to monitor and steer your agents from your phone.
- iOS: Download on the App Store or join TestFlight
- Android: Download APK 0.0.42
Community & Support
-
Discord: Join the community on Discord.
-
Twitter / X: Follow @orca_build for updates and announcements.
-
WeChat: Scan to join the Orca community WeChat group 7.
-
Feedback & Ideas: We ship fast. Missing something? Request a new feature.
-
Privacy: See the privacy & telemetry docs for what anonymous usage data Orca collects and how to opt out.
-
Show Support: Star this repo to follow along with our daily ships.
Developing
Want to contribute or run locally? See our CONTRIBUTING.md guide.
Signed Builds
Windows code signing sponored/provided by SignPath.io, certificate by SignPath Foundation.
License
Orca is free and open source under the MIT License.