Plexus
Download

Parallelwithoutchaos.

Plexus runs many Claude Code sessions side by side, each in its own git worktree, and shows you which one is working, which is idle and which one needs you.

DownloadRead the docs

macOS, Windows and Linux. Plexus drives the claude CLI you already use, on your own subscription. No API key, and your code stays on your machine.

Demo. The real Plexus window, running simulated sessions.Click a bar, a row or a prompt option.

Right now, in the demo

Each bar is as wide as the number of sessions in that state.

00.0 / 25 s

Parallel sessions, one glance.

Every session sits in a tree under its workspace and project, with one word for what it is doing: Working, Needs you, Delegating or Idle. A session that stops at a permission prompt or finishes its turn is counted in the sidebar's pill.

The Dashboard puts every session from every workspace in one table, the ones waiting on you first, with each branch's pull-request state beside it.

Sessions & status in depth In the docs: Sessions, Status, Dashboard

Review it like a pull request.

The Review tab shows what a session changed against its base branch, file by file, before anything is pushed. Comment on a line and send it to the agent, run an AI review, or start a Review and fix cycle that re-reviews until no issues are left or the round limit is reached.

Review in depth In the docs: Review

A worktree per session. Hooks at three levels.

Session checkout-flow, Git tab: only what changed in its worktree.

Each session gets its own directory and its own plexus/<name> branch, so agents never write over each other. Its Git tab shows only that worktree's changes, with a BASE line where the branch left its base.

Hooks run your scripts when a worktree is created, when the agent runs and when the session is torn down. Set them once globally, per workspace or per project. The resolved plan shows exactly what will run, in order, and where each step came from.

Worktrees & hooks in depth In the docs: Worktrees, Hooks

Settings, Worktrees & hooks for the project storefront.

A git client, and your issues.

Each project has a Git tab: the full graph with every session branch, what each session is doing at its branch tip, the refs and worktrees one click away in the rail, and Pull, Push and Stash in the toolbar. You can watch plexus/<name> branches leave main and come back through their pull requests.

Open a project's GitHub issues, or a GitHub Projects board, without leaving the window. Start session on any issue or card creates the worktree and links the session to it.

The Issues list and the board are part of a paid plan. Sessions, worktrees, review, the git client, pull requests and hooks never need one. See pricing or Plexus for teams.

Git & issues in depth In the docs: Project Git, Pull requests, Issues, Boards

How it compares.

Each comparison links the other tool's own documentation and says when it was checked.

Questions, answered.

Do I need an API key?

No. Plexus wraps the real claude CLI and hands your existing Claude Code sign-in to each session, so the agents run on your own subscription. Install Claude Code first and make sure claude --help works.

Which platforms does it run on?

macOS (Apple Silicon and Intel), Windows (x64) and Linux (x86_64, as .deb or AppImage). It needs Git on your PATH, and it updates itself after the first install. See the requirements.

Does my code leave my machine?

No. Your code, files, repositories, terminal sessions and the prompts and output you exchange with agents stay on your device. Pull-request features talk to GitHub or Bitbucket directly from your machine, with the account you connect.

What does Plexus send?

One anonymous usage message a day: operating system, processor type, app version, a random install identifier that is hashed under a key that changes daily, how much each feature was used since the last message, and coarse settings such as theme, model and project counts as a range. Never code, prompts, paths, repository or branch names.

Set DO_NOT_TRACK or PLEXUS_NO_TELEMETRY before launching and it sends nothing. Details are in the Privacy Policy.

Does it work with agents other than Claude Code?

Not today. Plexus is built Claude-first: Claude Code is the only agent it runs. Other coding CLIs are meant to plug in behind the same seam later.

Do I need a Plexus account?

No. Sessions, worktrees, review, the git client, hooks, pull requests and the dashboard work without signing in. An account is optional, and only needed for things like cross-device sync.

Is it free?

The core of Plexus is free. A paid plan adds things on top, such as cross-device sync, prompts saved to your account, organization features and the Issues list and boards. Prices are on the Pricing page.

Install Plexus.

Installation guide in the docs

Every build is on the public releases page, and the download page lists them all. Requires Claude Code and Git.