Treq vs Superset
Two local-first ADEs for different workflows: stacked changes or broad agent control.
Treq and Superset both run coding agents in isolated workspaces and give you a place to review the result. They sit in the same product category, but the workflow changes after the agents start writing code.
Treq is built around human review, stacked workspaces, and auto-rebase for AI branches. Superset is built around running many CLI agents in parallel. It also sells paid plans for teams.
At a Glance
| Treq | Superset | |
|---|---|---|
| Positioning | Stacking ADE, open-source Graphite alternative | Code editor for AI agents, software-factory platform |
| Isolation model | Jujutsu workspaces over a colocated Git repo | Git worktrees per task |
| Review surface | PR-style diffs, line comments sent back to the agent | Diff and file review inside the app |
| Stacked changes | Core workflow | Not emphasized publicly |
| Auto-rebase | Core workflow | Not emphasized publicly |
| Provider model | Claude, Codex, and Cursor shown today | Very broad CLI agent support |
| Remote or cloud workspaces | Not public on the site today | Remote workspaces and enterprise packaging |
| License | Apache 2.0 | Source-available under ELv2 |
| Pricing | Free and open source | Free tier, Pro, and Enterprise |
What Each Product Does
Treq is a desktop Stacking ADE. Each agent gets an isolated workspace with its own working copy, terminal, and line of history. You can arrange dependent workspaces into a stack, review each layer, and send comments back to the agent. When a lower layer moves, Treq rebases the workspaces above it and shows any conflicts.
Superset is a local-first desktop workspace for many coding agents. It launches CLI agents in isolated Git worktrees and adds chat, browser, review, and automation tools. Its public materials focus on parallel scale, integrations with GitHub, Linear, and Slack, plus paid plans for teams.
Both products solve the same basic problem. Several agents should not work in one shared checkout, so each task gets its own directory.
Feature Comparison
| Feature | Treq | Superset |
|---|---|---|
| Local-first desktop app | Yes | Yes |
| Parallel agent sessions | Yes | Yes, with an explicit 100+ agent ambition |
| Workspace isolation | Yes | Yes |
| Review and diff UI | Strong emphasis | Yes |
| Comments sent back to the agent | Yes | Review surfaces exist, agent-loop feedback is not the center of the public pitch |
| Stacked PR or stacked workspace support | Yes | Not emphasized publicly |
| Auto-rebase and conflict handling | Yes | Not emphasized publicly |
| Automations and scheduling | Not public on the site today | Yes |
| Remote or cloud workspaces | Not public on the site today | Yes |
| Open source | Apache 2.0 | Source-available under ELv2 |
Where They Differ
Both products run parallel agents in isolated workspaces. Their workflow models differ after the agents begin writing code.
Treq organizes agent work as linked, reviewable layers. Diff comments return to the agent, while auto-rebase keeps the stack current. This model fits features that need several small changes in a fixed merge order.
Superset focuses on breadth. Its public materials feature provider coverage, automations, remote workspaces, and team plans. This model fits teams that want one control plane for many agents.
Running many agents is becoming a standard feature. Treq's distinction is the stack that connects their work. That workflow must track each dependency, review layer, and rebase.
Pricing and Licensing
Treq is free and open source under Apache 2.0. There is no public paid plan today.
Superset offers a free tier, Pro pricing around $15 per user per month when billed yearly, and custom Enterprise pricing. Its desktop code is source-available under Elastic License 2.0, which is not the same as Apache-style open source.
In both cases you still pay the underlying model providers for Claude, Codex, or any other agent usage.
Who Should Choose Which
Choose Treq if you:
- Care more about reviewing and shipping AI-generated code than about launching the largest number of agents.
- Want stacked workspaces and automatic rebasing as part of the default workflow.
- Prefer Apache 2.0 open source and a local-only review loop.
- Are looking for a Graphite-like stacked workflow built for coding agents.
Choose Superset if you:
- Need broad CLI agent support and frequent provider switching.
- Want remote workspaces, automations, and team or enterprise packaging today.
- Prefer a product that already has pricing pages, compare content, and self-serve team plans.
- Care more about orchestration breadth than stacked PR discipline.
Next Steps
- Treq vs Conductor: Mac-native agent workspaces versus stacked review workflows.
- Treq vs Graphite for AI teams: why stacked PR tooling matters once agents write most of the code.
- Human-in-the-loop review workflow: how review comments become the next agent prompt.
- Stacked PR workflow: how dependent branches stay reviewable.
- Installation: install Treq and open a repository.