* Share Codex account history through folder links into ~/.codex Each Codex account home keeps its login; its history folders become folder links (junctions on Windows) into the user's ~/.codex, and Codex's databases follow through a sqlite_home line in the account's own config. Migration is automatic before the next launch in each home; the store's copy wins a name conflict and the account's copy is kept beside it. The per-file history bridge, its link pass and the WSL bridge are removed. Claude's merge-then-link moves to a shared async module both providers use. * Make account history moves safe under concurrency and keep the DB with the folders Files move by link-then-unlink so a move never replaces an existing name, host passes run one at a time per store, index markers are written before a move, account-only folders are shared, lock folders are moved rather than deleted, and sqlite_home is written only once a home's sessions are linked. * Let the history pass own sqlite_home, link locks first, and index per store The pass that links a home's folders now writes and removes its sqlite_home line; the config mirror only carries it forward. thread-writer-locks is linked before any history, index markers are kept once per store (hard-linked duplicates included), WSL links the launched home before Codex starts, passes queue per home in request order, and re-sharing after off then on works with earlier conflicts still kept. * Never overwrite on move, gate indexing on moves, and read the shared DB for backfill Files move by link or exclusive copy; repeat conflicts get their own pending folder; secrets and sandbox setup stay per home; the sqlite_home write retries against a concurrent mirror; indexing waits until no move is running; backfill checks read the DB where sqlite_home puts it. * Keep live writers' files, require both history links, and keep unmoved history on removal Files move only by a new name for their inode; a home is shared only when sessions and archived_sessions both link; reverted-thread rollouts get index markers; settled homes skip repeat passes in either mode; account removal keeps a real history folder. * Give resume test runtime-home mocks the account history step * Keep unmoved WSL history on removal, prepare the launched home, and retry incomplete work WSL account removal keeps real sessions/archived_sessions; a launch prepares the account it returns even if the selection changed meanwhile; an incomplete unshare and a failed WSL index pass stay eligible for a later launch; the guest helper rechecks the distro before each step. * Keep pinned resumes reachable, finish interrupted unshares, and keep index work from racing moves A pinned resume only shares; a launch re-prepares when the selection or setting changed; Orca's sqlite_home line is read only at the config root; a writer-lock link elsewhere keeps the home private; an unshare finishes its database move on retry; indexing keeps markers a newer move recorded, retries an incomplete run on a later launch, and merges WSL marker lists. * Move account history into a store one pass at a time and retry incomplete moves Two homes merging into one store at once raced on its folders and stranded the second home's history in its merge folder. Passes now run one at a time per store (host) and per distro (WSL), a folder that appears mid-move is merged into, and a share with failed moves is not settled. * Keep one rollout form in ~/.codex, record what sharing left behind, and guard Windows homes from older builds - A rollout present as .jsonl and .jsonl.zst lands in the store in one form only; the other form moves to the home's .orca-set-aside-rollouts, never deleted. - Each account home gets a versioned cleanup manifest: set-aside databases, left-behind rollouts with a background content check against the store, store twin pairs, and the shared streak. - Native Windows homes get a renamed ownership marker before their first junction, so older builds refuse to use or delete them. - Account removal keeps the set-aside rollouts and the manifest. * Set a rollout form aside only beside its twin in the store, inventory leftovers off the launch path, and keep account databases on removal - The .zst moves first and a form is kept out only when the store already holds its twin, so a failed move never leaves the store with neither form. - The rollout inventory and store twin walk run in the detached check, not the awaited pass; manifest writes are serialized per home and a check applies only to unchanged files; checkpoints are time-spaced. - A WSL check that runs out of budget resumes on a later launch instead of looping. - The ownership check reads either marker in one step and the marker rename retries on Windows. - Account removal keeps the account's Codex databases for the later cleanup release. * Read the cleanup manifest through a type guard * Read the cleanup manifest through a type guard over unknown * Settle only a check's own request, skip queued WSL passes after quit, and validate manifest entries - A pass finishing during a check keeps its new check request on host and WSL. - A WSL pass queued before quit no longer starts guest work. - Manifest rollouts must carry a path, size and mtime to be read. - The store twin scan reuses the twin module's folder walk. * Walk the store outside the manifest write and keep databases on removal only for shared homes - The inventory writes only its own fields onto a freshly read manifest, so it never undoes a streak reset from another process and a launch never waits behind the walk. - Account removal keeps the home's Codex databases only when the cleanup manifest shows the home was shared. * Lock the cleanup manifest across processes and validate every field later passes read - Manifest writes take a file lock, so a WSL check helper can't publish over another helper's streak reset. - The guard also checks storePath, the content check's store facts, database entries and sharedPasses; anything else is rebuilt from disk.
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 orca.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
# Release candidates (conflicts with the stable cask; uninstall it first)
brew install --cask stablyai/orca/orca@rc
# 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 an 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.













