* feat(native-chat): show a card for pull requests a chat turn opened When a turn's own command runs gh pr create and prints the new URL, the chat shows an "Opened orca#3" card under that turn with the PR's state, title and changed lines, read live from GitHub. The eye-slash control hides the card kind and a toast links to the new Settings switch. * fix(native-chat): satisfy lint in the opened pull request card * fix(native-chat): keep opened pull request cards through tool runs and failed rereads The card now rides a turn's work run, a clipped create output is always read whole (retried when the chat is shown, never while hidden), older Codex JSON output is decoded, rereads keep the last answer and restart past an in-flight read, failing lookups back off, and a failed hide save says so. * fix(native-chat): detect pull requests Codex opens through PowerShell, and wait for clipped output Codex on Windows runs commands as pwsh -Command '...', which detection now unwraps (and cmd /c), with tests on Claude's and Codex's recorded calls. A clipped create output is decided from its whole text, each message is scanned once, rereads keep their bytes counted, a merged card rereads after an edit, and the header names another repo's pull request in full. * fix(native-chat): retry each clipped pull request output until its host answers Each create output cut short on the wire keeps its own backoff while the chat is visible; a host whose support is unknown stays pending, and only one that says it can't give outputs whole is decided from the head. PowerShell options and backtick escapes are read as PowerShell does. * fix(native-chat): read PowerShell create commands in PowerShell's own quoting Decoding a tool call's script moves to its own module. PowerShell launches are lexed with its quoting (single quotes keep backticks literal, double quotes and bare text escape with them, here-strings and comments are text) and launch options follow the common pattern's tables; what can't be read whole opens nothing. A cancelled retry no longer records a failure. * fix(native-chat): decode a launch wrapper inside a PowerShell tool call * fix(native-chat): read Codex's escaped quotes in a Windows PowerShell command Codex on Windows writes a double quote inside a double-quoted -Command as \", so a create with an apostrophe in its title was skipped. Tests use the three calls recorded from Codex on Windows. * fix(native-chat): read a PowerShell launch line in the quoting of what ran it Codex joins argv in POSIX quoting even on Windows, splitting one word into differently quoted pieces, so a script ending in a backslash or holding both $ and an apostrophe showed no card. The launch line now goes through the same POSIX word decoder as the login-shell preview, and a PowerShell tool's own line through PowerShell's quoting. * fix(native-chat): find a PowerShell or cmd launch anywhere in a command list A Bash call such as `pwsh -Command 'gh pr create --fill' && echo done` lost its card once launch lines were read as POSIX words, and Codex's joined `cmd.exe /c 'script'` never had one. Each command in a POSIX list is now read on its own, through one launch reader shared with argv, while Node's Windows `cmd.exe /d /s /c "script"` form keeps cmd's own quoting. PowerShell lexing moves to its own module. * fix(native-chat): unwrap a PowerShell or cmd launch only when it is the whole line Rebuilding a command list around a nested launch could pull one out of a comment or heredoc into a false card, and an unreadable launch hid a real create beside it. As the common pattern does, only a line that is one launch is unwrapped; any other line is analyzed as written. A PowerShell tool's line and Node's cmd form must likewise be a single launch. * fix(native-chat): unwrap cmd and PowerShell-tool lines only when they are one launch Node's cmd form now unwraps only a /c script that is one quoted string with no quote inside, since cmd escapes none, and a PowerShell tool's line ends at a bare line break. Text after either launch can no longer pass for its script. * fix(native-chat): read a PowerShell line continuation as a word break A backtick before a line break in a PowerShell tool's line joined the next line into the current word, so an argument on the next line could pass for a command after the launch. * fix(native-chat): unwrap only the launch shapes agents are recorded writing Hand-written readers for cmd launches and for a launch nested in a PowerShell tool's script kept letting printed text pass for a create. Only argv, a shell's whole -c line and Codex's Windows pwsh -Command line are unwrapped now; argv is never space-joined, and detection reads a shell line as whole POSIX words rather than through the preview's lenient prefix. cmd launches and nested launches are intended misses until an agent is recorded using them. * fix(native-chat): read an escaped separator as text when finding a create An escaped \; stayed in the analyzed commands and passed for a separator, so printf '%s\n' \; gh pr create showed a card though only printf ran. Escaped characters are now text, like quoted strings and comments. * fix(native-chat): remove a line continuation when finding a create Blanking escapes also turned a backslash-newline into a word, so a create on the line after a continuation no longer started a command and lost its card. A continuation is now removed, as the shell removes it. * fix(native-chat): treat only backslash-LF as a line continuation Bash removes a backslash before LF but not before CRLF, where the backslash escapes CR and LF still ends the command. Removing both lost the card for a create on the line after a CRLF continuation.
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.













