Orca Gains 1,590 Stars in a Day and Answers Three of crystl's Six tmux Limits, With 4,303 Open PRs
Software / news
Orca Gains 1,590 Stars in a Day and Answers Three of crystl's Six tmux Limits, With 4,303 Open PRs
The MIT-licensed worktree app for coding agents has 98,318 stars and 4,306 open issues; its README addresses three of the six tmux limits crystl lists.
Orca, an MIT-licensed desktop app that runs coding agents side by side in separate git worktrees, gained 1,590 stars today on GitHub's trending list and stands at 98,318. Its README lists features aimed at the exact gaps a macOS terminal vendor's tmux guide calls "the ceiling."
Both documents are vendor material. Neither has been tested here, and each describes its own product favourably.
The tmux workflow, and where it stops
The tmux guide comes from crystl, which sells a macOS terminal app for Claude Code, and its last section recommends that product. The guide itself is specific. Claude Code's --worktree --tmux flags cover one agent on one branch, and --tmux requires --worktree. On iTerm2 the flag opens native panes, so the guide says to use --tmux=classic for real tmux.
Scripting other agents means tmux send-keys -l for literal text, then a separate Enter, with a sleep 0.3 between them because an agent's input box can swallow an Enter that arrives too early. Reading output back uses capture-pane -p -J -S -200. The guide's own line on the approach: "Silence is a proxy for done, not a report of it."
Six limits, and what Orca's README says about each
The guide lists six limits of tmux for agent work. Set beside Orca's README, three of them have a matching feature and three do not.
| crystl's tmux limit | What Orca's README says |
|---|---|
| No visibility into which agent is parked | "Notifications and unread state": know when an agent finishes or needs attention |
| No completion notification | Same feature, plus a phone app that notifies when an agent finishes |
| Nothing survives a reboot | Terminal scrollback "that survives restarts" |
| Brittle screen scraping | Not addressed |
| No shared state across sessions | Not addressed |
| Expensive scrollback across many agents | Not addressed |
Every Orca entry in that table is the project's own description. This article did not test whether the notifications fire when an agent is waiting rather than working, which was the tmux guide's complaint.
What Orca adds to the permission surface
A tmux session holds terminals and nothing else. Orca's README lists more. Its "Computer Use" feature lets agents "operate desktop apps and visible UI when a workflow needs real interaction." Its account switcher can "hot-swap accounts without re-logging in" for Claude and Codex, which means the app holds credentials for more than one account. A mobile companion pairs with the desktop host through a relay whose source sits in the repository's cloud/ directory.
The README says Orca "Works with any CLI agent" and names agents from Claude Code and Codex to Kiro and Rovo Dev. On telemetry it links to a docs page "for what anonymous usage data Orca collects and how to opt out" rather than stating it. That page was not read.
4,306 open issues and 4,303 open pull requests
The repository was created on March 17. GitHub's API shows 6,268 forks and an MIT licence. The latest release, v1.4.230, was published on October 19, and the 100 most recent releases include 12 dated October 1 to 19.
A GitHub search finds 4,306 open issues and 4,303 open pull requests. The README says "we ship daily, so this list is perpetually behind" and calls the changelog "the real feature list." Stars measure attention, and the open counts measure what is unresolved.
Orca's parallel pitch is "Fan one prompt across five agents, each in its own isolated git worktree," then compare and merge. That multiplies diffs a person must read. The README's answer is a review feature that lets you comment on diff lines and send them back to the agent.
What to check before installing
The tmux guide's recommendation is plain: keep tmux for remote boxes, long-running servers and fragile SSH links. Orca's README offers SSH worktrees with auto-reconnect and port forwarding, so the two overlap on the remote case.
Orca's releases page is the thing to watch. Its changelog is the only complete record of what the app can do, and at 12 releases in 19 days it will have moved again before most readers finish evaluating it.
Earlier coverage of agent tooling on this site: Agent37's sandbox pricing and Google Research's Harness2 repository.
Sources
More in Software
- 01OpenCode Has 217,837 Stars and a Security Policy That Says Its Permission Prompts Are Not a SandboxThe MIT-licensed coding agent's SECURITY.md tells users to run it in a Docker container or VM; its README labels the curl-to-bash install "YOLO".
- 02CLI-Anything Has 55,252 Stars and Three Test Totals, and Its Per-Harness Lines Sum to 2,622The HKUDS project that wraps desktop software for coding agents reports 2,461, 2,464 and 2,280 passing tests in one README, and its last push was Sept. 22.
- 03Linux 7.3 Ships With 18,765 Commits, a Filesystem That Fails Everything and Per-Cgroup BPF SchedulersLinus Torvalds released the kernel on Oct. 18 after a final week he called uneventful, with the biggest figures coming from storage and memory fixes.
- 04KiviDB Claims 21.2 Million GETs a Second, but Its Own Table Has Dragonfly Ahead Without PipeliningThe Rust, AGPL-licensed Redis-compatible store has 208 GitHub stars, no named authors and a benchmark run by its own company.