* fix(workspace-cleanup): let select-all include the workspace you are in Deleting the current workspace is allowed like any other, so select-all now includes it; a live agent stays excluded. Cleanup removal now hands focus to a surviving sibling after the batch, as the sidebar's batch delete does. Linear: STA-4686 * test(workspace-cleanup): cover focus handoff after the dialog closes and after Delete anyway * fix(workspace-cleanup): move focus off a deleted active workspace as soon as its row is gone * fix(workspace-cleanup): don't reopen a workspace the user left while a cleanup batch runs The per-row focus handoff fired whenever no workspace was selected, so closing the successor's last tab mid-batch re-activated it (and spawned a new terminal) on the next row. Move focus only when the workspace the batch left the user on is actually gone and nothing else took focus. * refactor(workspace-cleanup): move focus off the active workspace when a cleanup delete starts Switch to the successor once, right after the batch rows are marked deleting, instead of repairing an empty selection after each row settles. The active row is no longer active when it is removed, so the store never clears the selection and no later handoff is needed. * fix(workspace-cleanup): never hand focus to a workspace in the same cleanup batch The scan qualifies local rows as host `local`, so their delete state lives under a host-qualified key, while a sidebar row with no stored host only matches an unqualified key. The successor picker therefore saw batch rows as not deleting and could focus one about to be removed, leaving an empty screen once it went. Exclude the batch's own ids directly. * test(workspace-cleanup): use scan-shaped hosts in the active-workspace focus tests Candidates now carry the `local` host the scan publishes, which is what exposed the picker gap. The other-host case also stamps the viewed row with its host so it resolves; before, the lookup missed and the test passed with the host check removed. * feat(workspace-cleanup): confirm before a cleanup delete stops a running agent A cleanup delete (bulk, single row, or "Delete anyway") that includes a workspace with a running agent now shows a step naming those workspaces before anything is queued. The check reads live agent state at click time, attributed like the sidebar so structured chats count too, and re-asks if another agent starts while the step is open. The approved candidate records which agents the user agreed to stop; the per-row preflight that runs right before each delete refuses a row whose agent started after confirmation. With the step in place, live-agent rows join select-all like the active workspace. * refactor(workspace-cleanup): name the agent-stop same-action check * fix(workspace-cleanup): drop an open agent-stop step when the dialog reopens mid-batch * style(workspace-cleanup): match the agent-stop step's heading to the delete step * test(workspace-cleanup): type the cache-hydration mocks in the reopen test * style(workspace-cleanup): let the agent-stop step's heading use the dialog's own typography The changed-lines design-system gate rejects restyling DialogTitle and DialogDescription; the delete step's overrides predate that gate. * fix(worktree-delete): key delete state by the identity the sidebar card reads A cleanup delete names local rows with the 'local' host, so their queued and deleting state landed under 'local|<id>' while a card stored without a host reads the bare id and never showed it. Every delete-state write now derives its key from the store's own worktree record. * refactor(workspace-cleanup): reuse the sidebar delete's focus hand-off Drops the move-focus-before-delete path. Each confirmed row prepares the same prepareActiveWorktreeFocusAfterDelete committer the sidebar delete uses and runs it when that row's own removal succeeds, so the user stays on the workspace while it is queued, lands on the most recently visited surviving sibling once it is gone, and stays put if its delete fails. * refactor(workspace-cleanup): reuse the close-terminal stop-agent wording The stop step's single-agent title is the existing "Stop this agent?" string, and its description follows the close-terminal prompt's wording. * test(worktree-delete): cover a local-qualified removal failure on an unhosted card * docs(workspace-cleanup): describe the after-delete focus hand-off in the bulk-select note * fix(workspace-cleanup): name one agent in the stop step's button and keep one agent term per locale * fix(terminal): keep starting terminals in a workspace that is only queued for deletion A cleanup batch now marks its local rows with the same delete state the sidebar card reads, so the terminal spawn guard sees them. The guard exists because removal just killed the workspace's terminals; a queued row still has them and can fail its own delete and stay, so a new terminal opened there (often the current workspace) stayed blank. * refactor(terminal): name the teardown-started check the spawn guards share * chore(workspace-cleanup): keep one agent term in ko/zh and refresh a spawn-guard comment * fix(workspace-cleanup): refresh consent and focus per removal * fix(workspace-cleanup): invalidate detected host evidence * fix(workspace-cleanup): admit removal at transport send * test(workspace-cleanup): expect the send-time admission callback and a published chat tab
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
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)
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
- Android: Download APK · Install guide
Community & Support
-
Discord: Join the community on Discord.
-
Twitter / X: Follow @orca_build for updates and announcements.
-
WeChat: Group 11 is full. Scan to join the Orca community WeChat group 12.
-
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.
The relay that pairs the mobile app with a desktop host is also in this repository under
cloud/, with a separate pnpm workspace and setup 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.










