treq-dev · Ziinc · Jul 14, 2026 · Jul 15, 2026 · Jul 16, 2026 · Jul 17, 2026
diff --git a/web/compare/index.mdx b/web/compare/index.mdx
@@ -0,0 +1,21 @@
+---
+sidebar_position: 1
+description: Compare Treq's Stacking ADE with agent development environments, terminal tools, and stacked PR platforms.
+---
+
+# Compare
+
+_How Treq's Stacking ADE differs from other agent tools and stacked PR platforms._
+
+Treq is a desktop **Stacking Agent Development Environment (ADE)**. It gives each coding agent an isolated workspace, then connects dependent workspaces into a stack. Review and automatic rebasing keep each layer ready to ship.
+
+| Comparison | Best when you care about |
+| --- | --- |
+| [Treq vs Superset](./treq-vs-superset) | Broad agent control, team packaging, and review-focused workflows |
+| [Treq vs Conductor](./treq-vs-conductor) | Mac-native agent workspaces versus stacked review and rebase workflows |
+| [Treq vs Emdash](./treq-vs-emdash) | Cross-platform open-source breadth versus review and stack depth |
+| [Treq vs Claude Squad](./treq-vs-claude-squad) | Terminal tools versus a review-first desktop workspace |
+| [Treq vs Graphite for AI teams](./treq-vs-graphite-for-ai-teams) | Stacked PR tooling when agents write most of the code |
+| [Treq vs Orca](./treq-vs-orca) | Full IDE-like surface versus branch hygiene and review quality |
+
+New to the category? Start with [agent orchestration](/learn/concepts/ai-engineering/agent-orchestration), [git worktrees](/learn/concepts/git/git-worktrees), and [stacked PRs](/learn/concepts/git/stacked-prs).
diff --git a/web/compare/treq-vs-claude-squad.mdx b/web/compare/treq-vs-claude-squad.mdx
@@ -0,0 +1,90 @@
+---
+sidebar_position: 5
+description: Compare Treq and Claude Squad for multi-agent isolation, from terminal multiplexing to desktop review workflows.
+---
+
+# Treq vs Claude Squad
+
+_Same isolation idea, different control surfaces: desktop review versus terminal multiplexing._
+
+Treq and Claude Squad both start from git worktree isolation and parallel agent sessions. They serve different preferences for how much UI you want between you and the agents.
+
+Treq is a desktop Stacking ADE with PR-style review and automatic rebasing across dependent workspaces. Claude Squad is a terminal-native manager that uses tmux sessions and git worktrees for people who want minimal abstraction.
+
+## At a Glance
+
+| | Treq | Claude Squad |
+| --- | --- | --- |
+| Positioning | Stacking ADE for dependent agent work | Terminal-native manager for multiple AI terminal agents |
+| Control surface | Desktop app | Terminal UI over tmux |
+| Isolation model | Jujutsu workspaces over a colocated Git repo | Git worktrees plus tmux sessions |
+| Review surface | PR-style diffs and line comments | Basic or TUI-oriented review before push |
+| Stacked changes | Core workflow | Not emphasized publicly |
+| Auto-rebase | Core workflow | No public auto-rebase story |
+| Remote or cloud workspaces | Not public on the site today | No |
+| License | Apache 2.0 | AGPL-3.0 |
+| Pricing | Free and open source | Free and open source |
+| Distribution | GitHub releases and docs | Homebrew and GitHub |
+
+## What Each Product Does
+
+**Treq** gives each agent workspace its own working copy, terminal, and review surface. A target relationship connects dependent workspaces into a stack. You inspect each layer, send comments back to the agent, and let Treq rebase higher layers when their base changes.
+
+**Claude Squad** keeps you in the terminal. It manages multiple AI agent sessions through tmux, isolates work with git worktrees, supports background work, and expects review before push. The appeal is low abstraction and fast install for power users who already live in shell workflows.
+
+Both tools reject the idea that several agents should share one dirty working tree. Both keep the human responsible for what gets pushed.
+
+## Feature Comparison
+
+| Feature | Treq | Claude Squad |
+| --- | --- | --- |
+| Local-first | Yes | Yes |
+| Parallel agent sessions | Yes | Yes |
+| Git or VCS isolation | Yes | Yes |
+| Desktop review UI | Yes | No, terminal-oriented |
+| Comments sent back to the agent | Yes | Manual, outside a PR-style UI |
+| Stacked PR or stacked workspace support | Yes | Not emphasized publicly |
+| Auto-rebase and conflict handling | Yes | No |
+| Background agent work | Yes, per-workspace terminals | Yes |
+| Enterprise or remote packaging | Not public on the site today | No |
+| License | Apache 2.0 | AGPL-3.0 |
+
+## Where They Differ
+
+The main difference is the control surface. Claude Squad assumes you want tmux, a terminal UI, and as little desktop chrome as possible. Treq assumes review quality and stack maintenance deserve a dedicated interface.
+
+That leads to different failure modes. With Claude Squad, the cost shows up when review, comment routing, and stack rebases remain manual. With Treq, the cost shows up when you wanted a thinner tool and the desktop environment is more than you need.
+
+Licensing also differs. Apache 2.0 and `AGPL-3.0` create different obligations if you embed or redistribute the tool inside a larger system. For many individual developers that distinction never appears. For companies packaging internal platforms, it can.
+
+## Pricing and Licensing
+
+Both are free and open source.
+
+Treq uses Apache 2.0. Claude Squad uses `AGPL-3.0`. Install paths differ too. Treq ships through GitHub releases and product docs. Claude Squad ships through Homebrew and the project repository.
+
+Model provider costs are separate for both.
+
+## Who Should Choose Which
+
+Choose **Treq** if you:
+
+- Want a desktop diff and comment workflow that feeds the next agent turn.
+- Need stacked workspaces and automatic rebasing.
+- Prefer Apache 2.0 for company or platform use.
+- Are building a review-heavy process around AI-generated pull requests.
+
+Choose **Claude Squad** if you:
+
+- Prefer terminal-native tools and already use tmux heavily.
+- Want the lightest possible multi-agent control layer.
+- Do not need stacked PR UI, remote workspaces, or enterprise packaging.
+- Are comfortable handling review and rebase mechanics yourself.
+
+## Next Steps
+
+- [Treq vs Emdash](./treq-vs-emdash): open-source ADE breadth versus review depth.
+- [Treq vs Conductor](./treq-vs-conductor): another desktop orchestrator with a different product bet.
+- [Parallel development workflow](/learn/workflows/git/parallel-development): how isolated directories support concurrent work.
+- [Creating terminal sessions](/docs/tutorials/creating-terminal-sessions): terminals inside Treq workspaces.
+- [Installation](/docs/getting-started/installation): install Treq and open a repository.
diff --git a/web/compare/treq-vs-conductor.mdx b/web/compare/treq-vs-conductor.mdx
@@ -0,0 +1,90 @@
+---
+sidebar_position: 3
+description: Compare Treq and Conductor for parallel coding agents on the desktop, with a focus on review, stacks, and platform scope.
+---
+
+# Treq vs Conductor
+
+_Both run agents in isolated workspaces. Treq bets on stacked review. Conductor bets on a polished Mac workflow._
+
+Treq and Conductor solve the same first problem. Each coding agent gets its own workspace, branch, files, terminal, and review path. Their models diverge when tasks depend on one another.
+
+Treq is a Stacking ADE built around dependent workspaces, human review, and automatic rebasing. Conductor focuses on a Mac-native interface for running Claude, Codex, Cursor, and OpenCode agents as a team.
+
+## At a Glance
+
+| | Treq | Conductor |
+| --- | --- | --- |
+| Positioning | Stacking ADE, open-source Graphite alternative | Human interface to AI organizations on your Mac |
+| Platform | Desktop app, currently marketed for macOS | Mac-first desktop app |
+| Isolation model | Jujutsu workspaces over a colocated Git repo | Per-task workspace, branch, files, terminal, and diff |
+| Review surface | PR-style diffs with comments sent back to the agent | Diff and review path per task |
+| Stacked changes | Core workflow | Not emphasized publicly |
+| Auto-rebase | Core workflow | Not emphasized publicly |
+| Agent support | Claude, Codex, and Cursor shown today | Claude, Codex, Cursor, and OpenCode |
+| Cloud | Not public on the site today | Cloud early access |
+| Open source | Apache 2.0 | No public OSS repo surfaced |
+| Pricing | Free and open source | Download-first, public self-serve pricing not disclosed |
+
+## What Each Product Does
+
+**Treq** manages parallel workspaces for coding agents and keeps the merge path under human control. You inspect changes, leave line comments, and send that feedback back into the agent loop. Dependent workspaces can target each other as a stack. When a lower layer moves, Treq rebases higher layers and surfaces conflicts.
+
+**Conductor** is a Mac app for running a team of coding agents. Each task gets an isolated workspace with its own branch, files, terminal, diff, and review path. Public materials highlight Linear integration, multiple run scripts, and a download-first path that uses your existing Claude login. The product story centers on a polished human interface for AI teams. Stacked PR mechanics are not the public focus.
+
+Both products assume agents need isolation. Both assume developers still need a review step before merge. Neither is a general AI code editor. Both sit above the agents as a control layer.
+
+## Feature Comparison
+
+| Feature | Treq | Conductor |
+| --- | --- | --- |
+| Local-first desktop app | Yes | Yes, Mac-first |
+| Parallel agent sessions | Yes | Yes |
+| Workspace isolation | Yes | Yes |
+| Review and diff UI | Strong emphasis | Yes |
+| Comments sent back to the agent | Yes | Review path exists, agent-loop comments are not the public center |
+| Stacked PR or stacked workspace support | Yes | Not emphasized publicly |
+| Auto-rebase and conflict handling | Yes | Not emphasized publicly |
+| Issue tracker integration | Not public on the site today | Linear integration |
+| Cloud workspaces | Not public on the site today | Cloud early access |
+| Open source | Apache 2.0 | Closed source in public materials |
+
+## Where They Differ
+
+Conductor's public strength is commercial and product momentum. It presents a clear Mac-native workflow, strong growth signals, and team-facing motion. If your team already lives in Claude, Codex, Cursor, or OpenCode on macOS, that focus can reduce setup cost.
+
+Treq's workflow starts with the stack. A workspace can target another workspace, so dependent changes retain their merge order while agents work. Review comments return to the agent, and automatic rebasing keeps higher layers current when a lower layer changes.
+
+Platform scope also differs. Conductor's Mac-first story narrows the audience and sharpens the experience. Treq's open-source packaging makes inspection and contribution part of the adoption path. Cloud workspaces exist as early access in Conductor's public materials. They are not a public Treq offering today.
+
+## Pricing and Licensing
+
+Treq is free and open source under Apache 2.0. There is no public paid plan today.
+
+Conductor's site is download-first. Launch copy has described free use with an existing Claude login. Team and commercial terms also exist. Public self-serve pricing is not a clear bottom-funnel page in the same way as products with published Pro tiers.
+
+Model and agent usage fees remain separate in both cases.
+
+## Who Should Choose Which
+
+Choose **Treq** if you:
+
+- Need stacked workspaces and automatic rebasing for dependent AI changes.
+- Want PR-style review comments to drive the next agent turn.
+- Prefer Apache 2.0 open source and local review data.
+- Care more about branch hygiene and safe shipping than about Mac-native polish alone.
+
+Choose **Conductor** if you:
+
+- Want a polished Mac app centered on Claude, Codex, Cursor, and OpenCode.
+- Prefer a download-first product with Linear integration and cloud early access.
+- Care more about team orchestration narrative and commercial packaging than stacked PR tooling.
+- Are less concerned about open-source licensing for the orchestrator itself.
+
+## Next Steps
+
+- [Treq vs Superset](./treq-vs-superset): breadth and packaging versus review-focused orchestration.
+- [Treq vs Orca](./treq-vs-orca): broad ADE features versus a stack-native workflow.
+- [Changes and reviews](/docs/concepts/changes-and-reviews): how Treq turns diffs into agent feedback.
+- [Workspaces](/docs/concepts/workspaces): how stacked workspaces and rebases work.
+- [Installation](/docs/getting-started/installation): install Treq and open a repository.
diff --git a/web/compare/treq-vs-emdash.mdx b/web/compare/treq-vs-emdash.mdx
@@ -0,0 +1,90 @@
+---
+sidebar_position: 4
+description: Compare Treq and Emdash as open-source agent development environments, focusing on review, stacks, and provider breadth.
+---
+
+# Treq vs Emdash
+
+_Two Apache-licensed desktop ADEs with different models for multi-agent work._
+
+Treq and Emdash are open-source desktop ADEs for running many coding agents. Both isolate work per task and let you review the result. Their models differ when tasks depend on one another.
+
+Treq is a Stacking ADE built around linked workspaces and auto-rebase. Emdash supports more providers, remote work, prompts, skills, and built-in browser and editor tools.
+
+## At a Glance
+
+| | Treq | Emdash |
+| --- | --- | --- |
+| Positioning | Stacking ADE, open-source Graphite alternative | Open-source agentic development environment |
+| Isolation model | Jujutsu workspaces over a colocated Git repo | Parallel agent tasks with workspace isolation |
+| Review surface | PR-style diffs, comments sent back to the agent | Review surfaces 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 | 34 supported agent CLIs in public materials |
+| Remote work | Not public on the site today | SSH remote work, cloud workspaces, enterprise on-your-infra |
+| License | Apache 2.0 | Apache 2.0 |
+| Pricing | Free and open source | Free desktop app, enterprise and cloud contact motion |
+
+## What Each Product Does
+
+**Treq** keeps you in the merge path. Agents work in isolated workspaces. You review diffs, mark lines, and send comments back for planning or editing. A stack links workspaces that depend on each other. When a lower workspace updates, Treq rebases the layers above it and shows conflicts.
+
+**Emdash** is an environment for multiple coding agents. Its public materials feature parallel tasks and broad CLI support. Prompts, skills, MCP tools, an in-app browser, file editing, and issue handoff expand that environment. Emdash also supports SSH remote work and cloud deployment.
+
+Both use Apache 2.0, so licensing does not separate them.
+
+## Feature Comparison
+
+| Feature | Treq | Emdash |
+| --- | --- | --- |
+| Local-first desktop app | Yes | Yes |
+| Parallel agent sessions | Yes | Yes |
+| Workspace isolation | Yes | Yes |
+| Review and diff UI | Strong emphasis | 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 |
+| Broad provider support | Focused set today | 34 supported agent CLIs |
+| SSH or remote workspaces | Not public on the site today | Yes |
+| Cloud and enterprise packaging | Not public on the site today | Yes |
+| Open source | Apache 2.0 | Apache 2.0 |
+
+## Where They Differ
+
+Emdash covers more of the environment around each agent. It supports many providers, remote execution, cloud workspaces, and team deployment. This model fits teams whose agents run across different tools and machines.
+
+Treq makes the stack the main unit of work. Each workspace holds one reviewable layer and names the layer below it. Auto-rebase keeps higher workspaces current as lower workspaces change.
+
+Emdash has used more than one public domain. Some search indexes still show pages from an older product. Treq shares its name with unrelated products, including a Python package. These brand issues affect how people find each tool, but they do not change the product choice.
+
+## Pricing and Licensing
+
+Both desktop apps are free and open source under Apache 2.0.
+
+Emdash adds enterprise and cloud packaging through a contact-sales style motion. Treq does not publish a paid plan today.
+
+Agent and model costs remain outside either license.
+
+## Who Should Choose Which
+
+Choose **Treq** if you:
+
+- Want stacked workspaces and automatic rebasing as default behavior.
+- Care most about PR-style review that feeds the next agent turn.
+- Need an ADE where dependent agent tasks form a managed stack.
+- Are evaluating open-source options specifically for safe shipping of AI-generated code.
+
+Choose **Emdash** if you:
+
+- Need wide CLI provider coverage today.
+- Want SSH remote work, cloud workspaces, or on-your-infra enterprise options.
+- Prefer an ADE that includes browser, editor, prompts, skills, and MCP tooling in one surface.
+- Care more about environment breadth than stacked PR specialization.
+
+## Next Steps
+
+- [Treq vs Orca](./treq-vs-orca): another open-source ADE comparison with a different momentum profile.
+- [Treq vs Superset](./treq-vs-superset): packaging and breadth versus review focus.
+- [Agent orchestration](/learn/concepts/ai-engineering/agent-orchestration): why isolation and review matter once agents run in parallel.
+- [Code review workflow](/docs/tutorials/code-review-workflow): Treq's review loop in practice.
+- [Installation](/docs/getting-started/installation): install Treq and open a repository.