Treq vs Orca
Both isolate agents in worktrees. Orca expands the full environment. Treq deepens review and stack hygiene.
Treq and Orca are open-source ADEs. Each gives coding agents isolated workspaces and a place to watch the work. Their workflow models differ when tasks depend on one another.
Orca presents a broad environment with support for any CLI agent, built-in editing, browser and design surfaces, mobile access, and enterprise packaging. Treq is a Stacking ADE. It connects dependent agent workspaces, reviews each layer, rebases the stack as lower layers change, and sends conflicts back to the agent.
At a Glance
| Treq | Orca | |
|---|---|---|
| Positioning | Stacking ADE, open-source Graphite alternative | Agent development environment, worktree IDE for coding agents |
| Isolation model | Jujutsu workspaces over a colocated Git repo | Worktree per task, with terminal and browser tab |
| Review surface | PR-style diffs, comments sent back to the agent | Diff and Git tracking inside a broader ADE |
| Stacked changes | Core workflow | Not emphasized publicly |
| Auto-rebase | Core workflow | Not emphasized publicly |
| Provider support | Claude, Codex, and Cursor shown today | Any CLI agent |
| Extra surfaces | Desktop review and terminals | File editor, browser or design mode, mobile companion |
| Remote work | Roadmap: SSH remote development | SSH worktrees and enterprise packaging |
| License | Apache 2.0 | MIT |
| Pricing | Free desktop, Pro coming for GitHub and merge queue | Free and open source, enterprise contact motion |
What Each Product Does
Treq manages parallel agent workspaces and keeps merge quality under human control. You review changes, leave comments, and send that feedback back to the agent. Dependent workspaces form stacks. When lower layers move, Treq rebases dependents and shows conflicts. Conflict resolution is work the agent should do. You write instructions and include them in the review prompt.
Orca aims to be the place where agent work happens. Public materials stress per-task worktrees, terminals, browser tabs, a built-in file editor, and Git tracking. They also cover mobile support, automation copy, and paid team plans. The product story is a full environment for developers who already run many agents.
Both products accept that parallel agents need isolation. Both are open source. Both face pressure from vendor-owned agent apps that absorb these features over time.
Feature Comparison
| Feature | Treq | Orca |
|---|---|---|
| Local-first desktop app | Yes | Yes |
| Parallel agent sessions | Yes | Yes |
| Worktree or workspace isolation | Yes | Yes |
| Review and diff UI | PR-style diffs with line comments | Yes |
| Comments sent back to the agent | Yes | Broader ADE review, less public emphasis on stacked review loops |
| Stacked PR or stacked workspace support | Yes | Not emphasized publicly |
| Auto-rebase and conflict handling | Yes | Not emphasized publicly |
| Built-in file editor | Not the product center | Yes |
| Browser or design mode | Not public on the site today | Yes |
| Mobile companion | No | Yes |
| SSH worktrees | Planned, not shipped | Yes |
| Enterprise packaging | GitHub and merge queue listed as coming soon | Yes |
| Open source | Apache 2.0 | MIT |
Where They Differ
Orca's public momentum comes from breadth and speed. High GitHub traction, frequent releases, and a wide feature set make it look like a full environment for agent work. That is useful when you want one product for editing, browsing, mobile access, and remote worktrees.
Treq uses the stack as its primary workflow. Each workspace represents one reviewable layer and records which lower workspace it targets. Automatic rebasing keeps the dependency chain current while agents continue working. Isolation via worktrees, which Orca already has, does not rebase dependents when a base moves. Treq's workspaces use colocated Jujutsu for that rebase.
That creates a clear trade-off. Choose Orca when you want a full environment more than a specific merge workflow. Choose Treq when weak reviews, drifting stacks, and conflict-heavy AI branches are the costly failures.
Orca ships SSH worktrees now. Treq lists SSH remote development for later in 2026. Do not treat remote work as a current Treq capability.
Brand search is noisy for both. "Orca" collides with many unrelated products. "Treq" collides with an older Python package and other entities. Specific workflow pages matter more than bare brand queries.
Pricing and Licensing
Both desktop products are free and open source. Treq uses Apache 2.0. Orca uses MIT.
Orca also publishes enterprise packaging with a contact motion. Treq publishes Free and Pro. Pro is $15 per user per month. GitHub integration and merge queue are marked coming soon. Local review stays on your machine on both Treq plans.
Model and agent fees remain separate.
Who Should Choose Which
Choose Treq if you:
- Want stacked workspaces, automatic rebasing, and agent-driven conflict resolution as core behavior.
- Care most about PR-style review that returns comments to the agent.
- Need an ADE where dependent agent tasks form a managed stack.
- Want shipping of AI-generated code in reviewable layers as the main goal.
Choose Orca if you:
- Want a broad ADE with editor, browser, automation, and mobile surfaces.
- Need SSH worktrees or enterprise packaging today.
- Prefer any-CLI-agent flexibility as the primary buying criterion.
- Care more about environment completeness than stacked PR specialization.
Next Steps
- Treq vs Emdash: another open-source ADE comparison.
- Treq vs Superset: packaging breadth versus review focus.
- Treq vs Graphite for AI teams: why stacked workflows matter for agent output.
- Human-in-the-loop development: the review model behind Treq.
- Installation: install Treq and open a repository.