An owner-capable `pty.openClient` had two ways to fail that looked like something else. If the relay still held an owner record but the request carried no matching resume proof, admission fell through to a *subscriber* grant — a success-shaped response the client cannot use, which it then rejected with "did not grant an authenticated PTY session owner". And if the relay no longer held the record the client named, admission threw a stale-recovery error, which the client answered by deleting its own recovery row and reopening: two round trips, and the deletion took the `clientInstanceId` with it. Admission now returns an explicit outcome. Every `session-owner` grant carries `resumed`, so a client learns in one round trip whether its checkpoints survived. A resume proof for a record the relay has forgotten is not an error — it mints a fresh claim with `resumed: false`. A held claim produces one of two coded refusals instead of a subscriber grant: `PTY_CONSUMER_OWNER_HELD_ATTACHED_ERROR` is blocked and exits retry at once, `PTY_CONSUMER_OWNER_HELD_DISCONNECTED_ERROR` is transient and retried under its own bounded budget, separate from the publication-pending one so a settling publication cannot spend it. Nothing here destroys state on suspicion. A refusal mutates no checkpoint, owner, migration, or persisted recovery state, and `resumed: false` voids only the checkpoints taken under the lease the relay just replaced — the recovery row and `clientInstanceId` survive, guarded so a losing attempt cannot void a winner's. Shortening a disconnected incumbent's grace to a 250ms floor is gated on positive proof: that record reaches 'disconnected' only from an observed transport close, expiring it transfers admission rather than stopping any remote PTY, and the incumbent's own matching proof still wins outright because it never reaches that branch. A duplicate `pty.openClient` on one connection is now rejected even when identical. Two responses settle their publications independently, so one shared admission cannot make one response's rollback and the other's commit atomic; recovery from an RPC timeout opens a new connection instead. An attached-holder refusal is converted to a typed `SshOwnerAdmissionBlockedError` and routed through the existing terminal relay-error callback rather than transport reconnect classification — the relay answered and refused on purpose, so redeploy backoff would spend its whole budget on a link that is working. Verified by mutation: reverting each behavior turns a named test red — vacant-resume grant (1), held-owner refusals (5), grace clamp (1), duplicate rejection (2), `resumed` validation (4), refusal-triggered row deletion (1), the losing-attempt guard (1), attached-holder retry (2), the split retry budgets (1), and the blocked-error routing (1). Negative tests assert live sessions survive: a resumed claim keeps its checkpoints, the incumbent reclaims its lease during the shortened floor, a newer owner's record is untouched by a stale attempt, and a blocked refusal removes no recovery state. Refs STA-3365.
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
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.37
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.










