Quitting skipped the running-process confirmation unconditionally. That is correct in exactly one state: with the daemon adapter installed, quit's killAllPty() is a no-op against it and the shells are the daemon's children, which it declines to retire while a session is live — observed in production with a daemon and its PTY shells up 12 days against an app main started that morning. The bypass was written for that world but was never conditional on it, so in the degraded states — daemon init threw, the fail-open elapsed, or DegradedDaemonPtyProvider is installed and spawns fresh sessions in-process — the same silent quit killed live local processes with no warning and no way for the user to tell the two apart. Measured in an isolated node-pty probe: the foreground worker died both on an explicit kill and on a bare parent exit, while a detached-fork control survived. "There is no kill call" is not protection. Main now answers the one fact the renderer cannot see and sends it on window:close-requested as localPtysSurviveQuit, resolved per request from the existing daemonOwnsFreshPersistentPtys() — the adapter is installed, swapped and lost over a run, so a value captured at window creation would be stale. A quit skips the confirmation only on an explicit yes: a missing getter, a throwing read, an absent or non-boolean wire field all resolve to "does not survive" and ask, because an undetermined answer is not a yes. No fourth reading of "is anything running" — the probe is the one #17044 and #17077 settled, anyPtyBlocksWindowClose over readPtyProcessInspectionEvidence, with the whole verdict vocabulary unchanged. Pane selection moves next to it as collectWindowClosePtyIds. A quit drops panes on a RESOLVED SSH target: shutdown marks the lease detached rather than terminated and the remote shell is nohup-detached, so quitting ends nothing there and probing would only make the quit slower. Only a resolved target — getConnectionIdFromState answers undefined while the backing repo has not hydrated, and an unresolved host is not evidence the work survives, so those panes stay in. Nothing changes for an ordinary window close, which still probes every pane on its execution host, and nothing changes on a quit with a healthy daemon. No platform-specific behaviour is added: the gate is the same on all three, and the win32 minimize-to-tray branch still short-circuits ahead of it. No new stream opcode; the payload gains one optional-by-absence boolean that older readers already fall safe on.
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.46 · Install guide
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. If it is full, use group 8.
-
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.












