Compare
Trek vs Conductor
Both run coding agents in parallel, each in its own git worktree, on your Mac. Conductor wraps every workspace in a polished path from issue to merged pull request. Trek runs the agent CLIs you already use across every branch and repository, and keeps them going on a server of your own.
Checked against Conductor's docs, changelog and announcement in November 2026. Spot something out of date? Open an issue.
Conductor is winding down
On November 4, 2026, Conductor announced it is joining Meta. From that day new users can no longer sign up or download the app. Conductor Cloud goes read-only on November 13 and shuts down on November 20, and the local app keeps getting new models and critical bug fixes until early 2027.
- Nov 4No new sign-ups or downloads
- Nov 13Cloud workspaces go read-only
- Nov 20Conductor Cloud shuts down
- Early 2027Local app updates end
Choose Trek if you want
- A tool you can download today, with a road ahead of it
- The
claude,codex,geminiandgrokCLIs you've installed, plus local models - Agents that keep working on your own server after you close the laptop
- One agent leading the others from a built-in panel
- Projects that span several repositories, with workflow tags on every branch
Conductor may still suit you if
- You already have it installed and lean on its pull request flow: diffs, create PR, CI checks and merge
- You use setup, run and archive scripts with ports for every workspace
- You start workspaces straight from Linear or GitHub issues
- You run Cursor or OpenCode agents
- You want to drive your Mac from the iPhone app today
Side by side
| Trek | Conductor | |
|---|---|---|
| Availability | ||
| New users | Download and start today | No new sign-ups or downloads since November 4, 2026 source |
| Updates | Actively developed | New models and critical fixes until early 2027 source |
| Desktop app | macOS (Apple Silicon) | macOS source |
| Agents | ||
| Agents | Claude Code, Codex, Gemini CLI, Grok, local models | Claude Code, Codex, Cursor, OpenCode source |
| Uses the CLIs you've installed | Yes, in a real terminal, with your config, skills, plugins and hooks | Ships its own bundled Claude Code, Codex and OpenCode source |
| Local models | Ollama or LM Studio, through Claude Code | Not documented; custom providers such as OpenRouter, Bedrock and Vertex source |
| Coordination | ||
| Several agents on one branch | Session tabs per worktree | Several agents per workspace source |
| One agent driving others | Built-in Global panel with trek-dev MCP tools, on your own machines | API, CLI and MCP manage cloud workspaces, which shut down November 20 source |
| Several repositories in one project | Yes | Docs describe one repository per project source |
| Dev servers per worktree | A dev stack per worktree, on your Mac | Setup, run and archive scripts, with ten ports per workspace source |
| Tracking work | ||
| Issue tracker | Linear issue status and title on each branch | Start a workspace from a Linear or GitHub issue source |
| Workflow tags on branches | In Progress, In Review, Ready to Deploy and more, with a sidebar filter | Not documented |
| Notes | Kept with the branch, even after its worktree is deleted | Notes and handoffs in the workspace's .context folder |
| Git and pull requests | ||
| Diffs | A Changes view of each worktree | Diff viewer with review comments from GitHub source |
| Create, check and merge PRs | Not yet; check out a PR as a worktree and link PRs to branches | Create PRs with drafted descriptions, follow CI checks, merge source |
| Git hosts | GitHub | GitHub |
| Remote and privacy | ||
| Keeps working when you close the laptop | Run trek-server on any macOS, Windows or Linux machine you own | Only in Conductor Cloud, which shuts down November 20; local sessions stop source |
| Mobile | iOS and Android coming soon | iPhone app that can control your Mac source |
| Accounts | None | Needs GitHub and an agent provider source |
| Analytics | None | Feature-use analytics and crash logs; local chats stay on your Mac source |
Yes Partly, or with a catch No Not in its docs
Moving from Conductor
Most of what you know carries over. Here's where it lives in Trek.
<repo>-<branch>+ on a repository checks a PR out as a worktree.context notes→Branch notes, kept even after the worktree is gone, and gathered in All Notestrek-server on a machine you own, so agents keep going after you close the lidReal CLIs
The guides you already trust.
Trek starts the claude, codex, gemini and grok
you've installed, in a real terminal, so your config, skills, plugins and hooks come along.
Local models work too, through Ollama or LM Studio.
Camp
A camp that doesn't close.
Conductor's way to keep agents running after you close the laptop was its cloud, which
shuts down on November 20. Trek's camp is trek-server, running on a Mac,
Windows or Linux machine you own, with no account and no analytics.
Expeditions
One guide leading the rest.
Trek's Global panel is an agent with tools to create worktrees, start sessions, queue prompts, read their terminals and wait for them, on your own machines. It can spread one plan across several repositories in the same project.
Trail log
Know where every branch stands.
Every branch carries a workflow tag, from In Progress to Ready to Deploy, along with its Linear issue, pull request and notes. Filter the sidebar by tag to see what's waiting on review and what's ready to ship.
Where Conductor is ahead today
Conductor built a lovely app, and some of its ground Trek hasn't covered yet. Its pull request flow takes a workspace from a Linear or GitHub issue through a diff viewer, PR creation with drafted descriptions, CI checks and review comments to merge. Its setup, run and archive scripts give every workspace its own ports, and its iPhone app can drive your Mac. If you already have it installed, it will keep working into early 2027.
Ready for the next leg?
Bring your agents, your branches and your repositories. Trek is ready when you are.