Brennan Benson
29a43a73ed
* feat(antigravity): sign this host's Antigravity chats in with the server's own Google sign-in
Start spawns the Antigravity ACP server exactly as a chat start would (pinned
runtime, private temp, owner-only chat folder), behind the launch gate that
first stops this host's running Antigravity chats, and asks it to authenticate
with oauth-personal. A host without a pinned server build refuses Start, as it
refuses chats. The server's sign-in line now yields its link (validated as
Google's sign-in page back to a loopback port here) instead of ending the
connection signed out. Link long-polls the flow's state (25 s, early on change),
Cancel ends it, a new Start replaces it, and it expires after 300 s. All run on
the execution host behind accounts.antigravity-chat-sign-in.v1 and need
accounts-admin. List reports chatSignIn {saved, signingIn}; saved is a stat of
the server's own token file, which Orca never reads.
* Retain unclosed sign-in children and detach ended polls
* Narrow sign-in regression launch fields
* Keep fake sign-in fixtures independent of host support
* fix(antigravity): chat sign-in never installs the server and keeps its flow on the shared revisioned state
Sign-in resolves the server exactly as a chat start does and fails with the
not-installed reason when no copy is found, instead of downloading one. Its
flow state is a RevisionedState, the same publish-and-wait primitive the
runtime installer uses; replacement, close proof and the Link wire are unchanged.
* fix(antigravity): the chat sign-in status names the running sign-in, so a client that comes back can follow and cancel it
chatSignIn gains an optional flowId while a sign-in runs. Before, a sign-in nobody watched held the
chats' fence for up to 5 minutes and no client could see or cancel it.
* feat(antigravity): clients follow this host's chat sign-in by revision, as they follow an install
* fix(antigravity): name the sign-in state apart from the sign-in function so the module parses
* fix(antigravity): chat sign-in status is pushed to subscribers, failures read as plain sentences
accounts.antigravityChatSignInSubscribe (no params) sends the full sign-in
status as a snapshot on subscribe, then one frame per state revision, and
closes with the transport. It replaces the accounts.antigravityChatSignInStatus
long-poll, its long-wait lane and the bounded revision wait, as the install
status already did.
A failed sign-in now tells the person what happened in plain words (no
subscription, account not eligible, not approved, not installed, or a
generic retry) and logs the raw error instead of showing it.
Stopping the running chats before a sign-in waits for every close to settle
before it reports, so the fence never lifts while a close is still running.
* feat(antigravity): finish a chat sign-in from the address pasted by hand
When the browser runs on another computer than the host (SSH or a paired remote host), Google's last page points at a port on the host that the browser cannot reach, so the sign-in never finished. accounts.antigravityChatSignInComplete takes that pasted address, checks it is Google's answer to this flow's own link (same loopback origin and path, one matching state, one code or error, no userinfo or fragment, a Google issuer if any), and sends it once to the server's listener on the host with a single direct GET. The flow shows a new verifying phase while the server finishes, and refuses a second paste.
* fix(antigravity): Cancel answers once the sign-in has unwound, so a chat sent right after it is not refused
* fix(antigravity): the sign-in reads its launch sources through the shared helper, keeping the session create support within its line limit
Main's file already sits at the limit, and the runtime method only forwarded to the helper.
* fix(antigravity): a rejected pasted sign-in address says what is wrong with it
Every bad address used to get one sentence. It now gets the specific one:
too long, not a complete address, not this sign-in's, not exactly one
Google answer, or not from Google. The checks themselves are unchanged.
* fix(antigravity): chat sign-in follows the server's answers and belongs to the client that started it
The host's chat sign-in status was a check that the server's sign-in file
existed, which says nothing about whether the sign-in still works. The
link came only from one printed line, a new Start from any device
silently replaced a running sign-in, and a second link replaced the first.
- The server's BROWSER is now a one-line helper run by Orca's own
executable in Node mode, which prints the link on error output; it is
checked before every server start, and the printed line is still read,
on standard output as well as error output. No browser opens on the
host, Windows included.
- A sign-in belongs to the client that started it. Others see it in
progress without its link and cannot start, cancel or complete it; it
ends on its own after five minutes.
- After Google answers, a session on the same server must start before
the sign-in reads as signed in.
- The host's status is the server's latest answer: signed in when a chat
session or the sign-in's session starts, signed out when a chat hits
the sign-in prompt or is refused for sign-in, and unknown until then.
Nothing is read from the sign-in file and nothing is saved.
- A second, different sign-in link fails the sign-in.
* test(antigravity): the launch parity record shows the sign-in link helper as the server's browser
* fix(antigravity): a sign-in owns its work until it has unwound, and reads only whole, valid sign-in lines
Problems in the previous round: a sign-in could read as finished while its
server or pasted-address request still ran, a server refusing a sign-in
after a chat started left the host shown as signed in, the checking
session stayed saved in the server's own store, and a broken sign-in line
could count as the server asking to sign in.
- The browser helper is POSIX only, with Node mode set inside the BROWSER
command; Antigravity chats are not offered on Windows.
- Sign-in lines are read by source: standard output carries the printed
line, error output the printed line and the helper's. Only a whole,
valid link is an answer; a malformed one on error output is dropped, and
on standard output it ends the server. Standard output goes through the
protocol's own line reader, including a last unterminated line, and
error output keeps a whole link while its diagnostic tail stays small.
- Any request the server refuses for sign-in marks the host signed out.
- A sign-in is the host's one operation from Start until its work has
unwound; a Start before then is refused, and Cancel or expiry also stops
a pasted address on its way to the server.
- A different second link fails the sign-in at any point, including while
it is being checked.
- The checking session's saved conversation is removed once the server is
proven gone, only when its metadata names the sign-in's own folder.
- A pasted address is checked for length before it is trimmed.
* Preserve ACP auth answer ordering and sign-in cleanup
* Fix ACP settlement lint and await sign-in cleanup in fixtures
* test: update Antigravity browser launch snapshots
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
Mobile CompanionMonitor and steer your agents from your phone — get notified when an agent finishes and send follow-ups from anywhere. |
 |
Parallel WorktreesFan one prompt across five agents, each in its own isolated git worktree — compare the results and merge the winner. |
 |
Terminal SplitsGhostty-class terminals with WebGL rendering, infinite splits, and scrollback that survives restarts. |
 |
Design ModeClick any UI element in a real Chromium window to send its HTML, CSS, and a cropped screenshot straight into your agent's prompt. |
 |
GitHub & Linear, NativeBrowse PRs, issues, and project boards in-app — open a worktree from any task and review without a context switch. |
 |
SSH WorktreesRun agents on a beefy remote box with full file editing, git, and terminals — auto-reconnect and port forwarding included. |
 |
Annotate AI DiffsDrop comments on any diff line and ship them back to the agent — review, edit, and commit without leaving Orca. |
 |
Drag Files to AgentsVS Code's editor with autosave everywhere — drag files or images straight into an agent prompt. |
 |
Orca CLIAgents drive Orca too — script every workflow with |
 |
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.