Neil
a3512fcd69
The LRU cap added in 20fb0b3f6e bounded memory by discarding a safety property.
Reported as a review concern, reproduced before believing it, and confirmed:
`sessionTabsPublicationEpochHistoryByWorktree` is deliberately RETAINED after a
worktree's live record is dropped — it is the tombstone fence that stops a
sibling stream's late frame from a retired publisher being applied. A pure LRU
evicts exactly those tombstones, by construction: a still-publishing worktree
renotes its epoch on every accepted frame, so the eviction victim is always a
fence.
Absence is fail-OPEN on both read paths. `hasRetiredValue` answers false for a
missing entry, so `isRetiredSessionTabsPublicationEpoch` cannot tell "never seen"
from "fenced and forgotten" — and `recordReceivedWebSessionTabsSnapshot` then
RE-NOTES the evicted epoch as current, resurrecting the publisher the fence
retired.
MEASURED, not argued. Fence a worktree, note 512+ others, deliver the retired
publisher's late frame: with the tombstone retained it is rejected; after
eviction it is ACCEPTED.
The first version of that repro passed and was wrong. It gave each worktree its
own runtime id, so the retired RUNTIME-ID fence rejected the frame and the epoch
fence was never consulted — a test green for an unrelated reason. A real sibling
stream on one environment shares the runtime id; with one shared id throughout,
the acceptance reproduces. Recorded here because the fixture detail is the whole
difference between a passing test and a real one.
THE FIX: the cap yields to the fence rather than the other way round. Each entry
carries `notedAt`, and eviction stops at the first entry younger than
SESSION_TABS_PUBLICATION_FENCE_RETENTION_MS. The map may exceed 512 while every
entry is still young; memory is then bounded by worktree churn WITHIN the
retention window instead of by count, which is the bound that can be held
without discarding a live fence.
512 IS NOT THE JUSTIFIED NUMBER, and it was right to challenge it — it was a
memory target with nothing behind it. The justified number is the retention
window: 4x the tab RPC budget. A frame in flight longer than that budget has
already been abandoned by the transport, so a fence older than 4x it has outlived
anything it could fence against. The count cap is now only the memory target, and
it is the one that gives way.
Both growth tests are updated to advance the clock, which also makes them
faithful: a long-running session is long in TIME, and a count-only fixture
measures the map at an instant where nothing is evictable and no bound can hold
without dropping a live fence.
Also writes the structural-assertion lesson into the teardown test's header
rather than leaving it in a commit message: the original perf assertion was a
wall-clock ratio that flaked at 22.3x against a 20x bound, and was replaced with
a `.keys()` spy, because the enumeration IS the cost. A duration assertion fails
for reasons unrelated to the property it protects and gets retried away, taking
the real regression with it.
Mutation: removing the retention guard (back to pure LRU) kills exactly the
"keeps a young fence past the cap" assertion, and leaves every bound assertion
passing — the bound tests and the fence test are cleanly separated.
Verification: 190 files / 1595 tests pass, log grepped = 0. pnpm tc and oxlint
clean.
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
OpenCode
MiMo Code
Amp
OpenClaude
Antigravity
Pi
oh-my-pi
Hermes Agent
Devin
Goose
Auggie
Autohand Code
Charm
Cline
Codebuff
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
- Running
orca serveon a headless Linux server? See the headless Linux server guide.
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 or join TestFlight
- Android: Download APK 0.0.48 · 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 8. Group 8 may be full; if so, scan the Group 9 QR code instead.
-
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.