* fix(terminal): a host with a window keeps a pane a client moved to a new tab Dragging a split pane onto the tab strip in a paired worktree whose host runs the desktop app with a window flickered and snapped back. The client draws the new tab and calls session.tabs.movePaneToNewTab, but the host answered not_held whenever it had a window, because the window owns the layout and only headless hosts committed the move. The client reverted, and even without the revert the host window's next snapshot would have rebuilt the old tab. Main now asks its window to make the move and waits for the answer, the way other client requests reach a window-owned host. The window moves the pane with its own drag-out path under the tab id the client already drew, at the client's drop position, mounting a parked source tab first. A pane the window cannot reach is refused, so the client puts it back; a host without the window bridge still answers not_held. Older clients and hosts are unaffected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(web): rely on the optional pane-move bridge instead of no-op stubs The web client never receives host pane-move requests, and the bridge already skips registration when these members are absent; dropping the stubs keeps web-ui-api.ts under the line limit after rebasing on main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(e2e): a window host keeps a pane a paired client moved to a new tab The window-host case asserted the old refusal, where the client drew the new tab and put the pane back. It now drags a pane out on a paired client and checks the pane stays in the tab the client drew: the host window holds the leaf alone under that tab id, no snapshot pulls it back, and the source keeps one pane. It fails on main, where the tab count falls back after the drop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(terminal): refuse a pane move the host window cannot answer When a paired client asks a host with a window to move a pane to a new tab, the host relays the request to that window. If the window is gone, closes, or does not reply within 10 seconds, the relay rejects. The host returned that rejection as an RPC error instead of a move result. The host now answers { status: 'refused', reason: 'pane_unavailable' } in that case. The client already puts the pane back on a refusal, and this is the reply the relay timeout was sized for. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(terminal): fence a window's pane move once the client heard it timed out The relay told the client "refused" after 10s but left the window's move running, so a late commit moved the pane on the host after the client had put it back. Main now fences the commit: a move the client was told timed out commits nothing, and a commit answers the client at once, before the deadline can turn it into a refusal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(terminal): keep the pane-move fence Electron-free and let a claimed commit answer The leaf-move IPC is shared with the plain-Node runtime, so the fence moves to its own Electron-free module. A window that goes away mid-commit no longer refuses a move its commit landed, and a second move cannot replace a fence a timed-out move still holds. Fixes #37082 * chore(terminal): follow moved shared modules after rebasing the pane-move relay Refs #37082 * fix(terminal): hold a client's pane move's source tab mounted until the move settles The timed split-mount lease could expire while the window was still moving the pane, so cold parking could unmount the source tab after main had already told the client the move landed. The move now holds the tab mounted for its whole duration and releases it when it settles. Fixes #37082 * fix(terminal): don't toast the host window for a pane move another client asked for Fixes #37082 * fix(terminal): relay a client's pane move only to a window that owns the layout Where main owns the layout (the dark ORCA_LAYOUT_OWNER=main path), the window's move goes back through main, which names its own tab, so the client's tab id could not be kept. Main answers not_held there, as before this change. Fixes #37082 * fix(terminal): name the renderer a relayed pane move belongs to Fixes #37082 --------- Co-authored-by: Seunghwan <hyunsh.cycle@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Orca
中文 · 日本語 · 한국어 · Español · Français · Português · Türkçe · Русский
The AI Orchestrator for 100x builders.
Run Claude Code, Codex, and any other coding agent in parallel, each in its own worktree. Chat or terminal, on your laptop or in the cloud, with diffs, a browser, and a CLI in one app.
Download Orca
Features
Also in the box:
- Drag Files to Agents: drag files from the explorer, or images from your desktop, straight into an agent's prompt.
- Jump Anywhere: one shortcut jumps to any workspace or tab across every repo and host.
- Rich Previews: open images, PDFs, and Markdown right in the workspace, next to the agent that made them.
- Mobile Emulator: run an iOS Simulator or Android emulator beside your agent, and let it tap, type, and check its own work.
- Dictation: press a shortcut and talk. Orca types what you say into the agent's prompt or terminal.
- Usage & Accounts: see how much of your agent limits you've used and when they reset, and switch accounts without logging out.
- Automations: schedule prompts to run on any repo: nightly dependency bumps, weekly triage, flaky-test sweeps.
- Computer Use: when there's no CLI or API, agents can see and drive desktop apps and external browsers.
- 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
Muse
DeepSeek Harness
ZCode
OpenCode
MiMo Code
Amp
OpenClaude
Antigravity
Pi
oh-my-pi
Hermes Agent
Devin
Goose
Auggie
Autohand Code
Charm
Cline
CodeBuddy
Codebuff
Freebuff
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
Or via a package manager:
# macOS (Homebrew)
# Always use the full name; bare `orca` is an unrelated Plotly cask.
brew install --cask stablyai/orca/orca
# Upgrade an existing install
brew upgrade --cask stablyai/orca/orca
# Arch Linux (AUR) — or stably-orca-git to build from source
yay -S stably-orca-bin
Mobile App — iOS, Android
Pair with your desktop app to monitor and steer your agents from your phone.
- iOS: Download on the App Store
- Android: Download APK · 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.
-
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 sponsored/provided by SignPath.io, certificate by SignPath Foundation.
License
Orca is free and open source under the MIT License.













