The Plexus
How to install the app, run your first sessions and use every feature, from the session tree to review, hooks and git. Written for the version you can download today.
Start here
- InstallationDownload and install Plexus on macOS (Apple Silicon or Intel), Linux (.deb or AppImage) or Windows, check Claude Code and Git, and get automatic updates.
- Getting startedYour first run of Plexus: add a git repository, create a session in its own worktree, start Claude Code and send your first prompt.
- Core conceptsWorkspaces, projects and sessions in Plexus — each session usually its own git worktree running Claude Code — and the two status indicators on every row.
Overview
What Plexus is, how to install it, and the model behind it.
- IntroductionPlexus runs Claude Code sessions in parallel, each in its own git worktree, in one native desktop app with diff review, a git client and hooks built in.
- InstallationDownload and install Plexus on macOS (Apple Silicon or Intel), Linux (.deb or AppImage) or Windows, check Claude Code and Git, and get automatic updates.
- RequirementsWhat Plexus needs on your machine: the Claude Code CLI and Git, plus optional GitHub or Bitbucket access, notify-send on Linux, and supported platforms.
- Getting startedYour first run of Plexus: add a git repository, create a session in its own worktree, start Claude Code and send your first prompt.
- Core conceptsWorkspaces, projects and sessions in Plexus — each session usually its own git worktree running Claude Code — and the two status indicators on every row.
- ArchitectureHow Plexus is built: a Tauri desktop app with a Vue UI and a Rust backend that wraps the Claude Code CLI, runs git natively and keeps your code local.
Working with projects
The dashboard across every workspace, the project's git client and its terminals.
- DashboardOne live table of every Claude Code session across your Plexus workspaces, with activity state, PR status, summary counts, filters and sorting.
- Project Git clientA full git GUI for a project's main checkout: commit graph with branches, tags, stashes and worktrees, pull, push, line staging, compare, blame, history rewrites, undo and conflict resolution.
- Project TerminalOpen plain shell terminals in a project's root folder from the project view. They keep running in the background, so a dev server or file watcher stays up.
Working with sessions
One agent per worktree: talk to it, follow its status, review its changes and ship them.
- Sessions & worktreesCreate a Plexus session — one Claude Code agent in its own git worktree, on a new or existing branch — and start, stop, resume, archive or remove it.
- Status & notificationsWhat Plexus's status dots and PR colors mean — working, waiting, idle, background work — and the alerts you get when a Claude Code session needs you.
- The Agent tabThe Agent tab is the Claude Code terminal in every session: send prompts, paste images, compose multi-line input, rewind, and choose the permission mode.
- Explorer & editorBrowse a session's git worktree and edit files in the built-in Monaco editor, with tabs, change markers against the base branch and a Markdown preview.
- Review & diffsReview a Claude Code session's changes as a PR-style diff, leave inline comments the agent acts on, run an AI code review and answer PR threads.
- Git workflowThe session Git tab lets you stage, commit, stash and push, and rebase, merge or squash a Claude Code session's branch, with AI-drafted commit messages.
- Pull requestsOpen a GitHub or Bitbucket pull request from a session's branch, let AI draft the title and description, and track PR and CI status without leaving Plexus.
- Stacks & ordered mergingStack Claude Code sessions on each other's branches, keep every branch synced as the stack moves, see the whole stack as a map, and merge a stack — or a list of pull requests — in order, including through GitHub's and Bitbucket's merge queues.
- TerminalOpen plain shell terminals in a session's git worktree with ⌘J: several tabs, copy and paste, drag-and-drop file paths, and your choice of shell.
- Split viewPut up to six sessions of one project side by side in a split view: each pane is a full session with its own tabs, and every agent keeps running whether its pane is on screen or not.
- Multiple windowsOpen a session, a project, a single terminal or the dashboard in a window of its own: put an agent on a second monitor and keep the main window for everything else.
Automation
Hooks, env files, ports, secrets and prompt templates that set sessions up for you.
- Lifecycle hooksRun your own shell scripts when a session's git worktree is created, when the agent starts, and at teardown — set globally, per project or in the repo.
- Worktrees & env filesWhere Plexus puts each session's git worktree, how .env and other gitignored files are copied in, and the block of dev server ports every session gets.
- SecretsPlexus keeps secrets in your OS keychain — macOS Keychain, Windows Credential Manager or Linux Secret Service — write-only, and out of every hook it runs.
- Prompt templatesSave Claude Code prompts you keep rewriting as templates with fill-in fields — text, choices, files, branches — and run them in a new or a running session.
Integrations
Git providers, issues and boards, Plnnrly, your Plexus account, organizations and sync.
- Connecting a git providerConnect GitHub or Bitbucket to Plexus with a one-click browser sign-in, no personal access token, to open pull requests, clone repos and push over https.
- Your Plexus accountCreate a free, optional Plexus account to set up organizations, manage signed-in devices and turn on cross-device sync. The app works the same without one.
- Plans, seats and billingWhat a paid Plexus plan unlocks, individual and per-seat organization plans, buying through Moneybird, invitations, invoices and VAT, and cancelling.
- Cross-device syncSync your Plexus settings, workspaces and projects to every machine you sign in on, after a preview of exactly what would leave this one.
- Roles and permissionsControl what each member of a Plexus organization may do: five built-in roles, custom roles you copy and edit, and how roles combine. Free, on the web.
- Shared workspacesSet up a workspace once in a Plexus organization so every member gets the same repositories in their sidebar: join modes, leaving, cloning, and seats.
- Managed settingsLet a Plexus organization recommend, enforce or dry-run settings on members' machines: the three levels, locked rows, eligible settings and offline rules.
- Prompts your organization publishesPublish Claude Code prompt templates to every member of a Plexus organization as numbered revisions: proposing, publishing, rolling back, limits and seats.
- Issues from your trackerRead, edit and create a project's GitHub issues inside Plexus with your own GitHub account, and start a Claude Code session that stays linked to an issue. Plnnrly has a page of its own.
- The ToolchainAttach GitHub issues, GitHub Projects boards and Plnnrly projects to a workspace or project as tabs in Plexus, and choose whether a workspace shares each with its projects.
- Boards from GitHub ProjectsWork a GitHub Projects board inside Plexus: attach it to a workspace or project, switch views, drag cards, open the issue behind a card, start a session.
- Plnnrly work items, boards and sprintsConnect a Plnnrly organization and work a Plnnrly project inside Plexus: its backlog, board and sprints, every work item editable, and a session started from any of them.
Reference
Every setting and shortcut, and how to send the team feedback.
- SettingsEvery Plexus setting and its default, and how settings layer from global to workspace, project and session — including organization-enforced values.
- Keyboard shortcutsEvery Plexus keyboard shortcut — session tabs, terminal and dashboard, ⌘K search, stack layers, the Claude Code prompt, rebase and squash, project Git undo — and how to rebind each.
- Sending feedbackSend a bug report or idea to the Plexus team from inside the app, with an optional screenshot and diagnostic logs you can preview before anything is sent.
Introduction
Plexus is a native desktop app for running several Claude Code sessions in parallel — each in its own git worktree — without juggling a dozen terminal tabs.
The core idea
You add a git repository as a Project (Projects live inside Workspaces), then spin up Sessions. Each Session is its own git worktree — on a fresh branch Plexus cuts for it, or on a branch that already exists — wrapping a named Claude Code session in a real terminal. Several agents run side by side, each isolated in its own worktree, so their changes never collide — and you always know at a glance which one is working and which is waiting for you.
The shape of it: Workspace ▸ Project ▸ Session. See Concepts for the model in depth.
What you get
- Parallel, isolated sessions. Every Session lives in its own worktree, so multiple agents work on different features at once without stepping on each other or your main checkout.
- Always know the state. A live status dot tells you which sessions are actively working versus waiting for input, alongside each session's branch and pull-request state — see Status.
- PR-style review. Read changes as a unified diff and leave inline comments the agent reads and iterates on, all inside the app — see Review.
- Built-in editor and git client. Browse and edit files in the worktree, then stage, commit, and manage branches without switching tools — from a per-session Git tab up to a full project-level git client with a commit graph and conflict resolution. See also Explorer.
- Three-level lifecycle hooks. Run your own commands at the global, workspace, and project levels to automate setup, checks, and teardown — see Hooks.
- Layered settings. Configuration cascades from global defaults down to per-project and per-session overrides, so each repo behaves the way it needs to — see Settings.
- The same setup on every machine. Optionally, your settings, workspaces and projects follow you to any computer you sign in on — after one dialog that shows you exactly what would leave this one. See Cross-device sync.
- Native, local, and fast. Plexus is a real desktop app that runs on your machine — it never sends your code or credentials anywhere.
Where to next
- Install — download a signed build and let it auto-update.
- Getting started — add a repository and run your first session.
- Concepts — Workspaces, Projects, Sessions, and worktrees explained.