Dashboard
One live table of every Claude Code session across your Plexus workspaces, with activity state, PR status, summary counts, filters and sorting.
The Global Dashboard shows every Claude Code session across all your workspaces and projects in one live table, so you can see at a glance which are working, which need you, and where each pull request stands.
It shows your active work only: archived sessions, and the sessions of an archived project, drop out of the table (and the header counts) until you restore them.
Open the dashboard
Press ⌘0, or click the Dashboard button in the left sidebar. (⌘ is Cmd on macOS, Ctrl on Windows and Linux.) Press ⌘0 or click the button again to toggle it off and return to the session view.
The right pane switches to a session table with these columns:
| Column | Shows |
|---|---|
| State | The activity dot — working, waiting, or idle — ringed in blue when background work is running |
| Session | The session name, and its state — Checks, Review, Ready, Behind, Merged, … |
| Project | The project the session belongs to |
| Branch | The session's worktree branch |
| Workspace | The workspace the project lives in |
Each row carries the same indicators as the navigation tree — a pulsing activity dot, a PR badge, and the session's state chip, which says where its pull request or its stack stands; an amber one means it needs you. A session in Merge in order also shows its place in the list, 1 of 3. See Status & indicators for what every color and icon means, and States for every chip.
Summary counts
A header above the table totals every session by state: green working (agents producing output), amber waiting (sessions that need your input), and gray idle (started sessions with no active turn), plus green open and purple merged pull-request counts. Every session lands in exactly one of the three state counts, so the three always add up to the number of sessions in view.
One more count appears when there is something to report: N delegating — how many sessions have background work running, such as background subagents or a workflow. Its glyph is a blue ring rather than a filled dot, matching the row indicator, because it cuts across the other three counts rather than adding to them: a session with delegated work running is still counted as working, waiting, or idle. Hover it for the breakdown — "3 background tasks running across 2 sessions". A workflow counts as one task however many agents it runs, and background shell commands aren't counted, since they don't light the ring. The chip is hidden when nothing is delegated.
Filter and sort
The Filter by workspace dropdown defaults to All workspaces; pick a workspace name to narrow the table to its sessions. Only the table is filtered — the summary counts stay global.
The Sort sessions dropdown reorders the table:
| Mode | Order |
|---|---|
| Needs input first | Waiting, then working, then idle (the default). Within each group, sessions with background work running come first |
| Recently active | Most recent activity first |
| Workspace | By workspace, then project, then session |
| Name | Alphabetical by session name |
Your sort choice is remembered while the app is open and resets to the default the next time you launch Plexus.
Jump to a session
Click anywhere on a row to focus that session: Plexus switches to the session view, selects the session, and expands its project and workspace in the sidebar tree. The one exception is the PR badge — clicking it opens the pull request in your browser instead.
If you already know which session you want, ⌘K gets there without the dashboard: it searches every session and project by name, branch, project or workspace. See Keyboard shortcuts.
In its own window
The new-window button in the dashboard's header opens the dashboard in a window of its own — a second, live copy, so you can keep it on another screen while the main window shows a session. Clicking a row there opens that session in the main window. A row whose session is already open in a window of its own shows a small window icon, and Open in new window in a row's ⋯ menu moves that session out. See Multiple windows.
The project dashboard
The same table exists scoped to a single project: click a project's row in the sidebar tree to open the project view, whose Dashboard tab lists only that project's sessions — the same columns and live indicators, summary counts for just this project, and the same sort modes (minus Workspace, which is meaningless within one project). A New session button sits in the header, so starting the next piece of work never leaves the view. As everywhere else, archived sessions are excluded.
The project view's tab strip holds Dashboard, Git and Terminal, then one tab for every tool in the project's toolchain — an Issues tab per repository (labelled Issues · owner/name when there is more than one) and a Board · name tab per GitHub project — and, at the right end, a Settings button that is not a tab: it opens the project's settings on the Toolchain page, where those tabs are configured. See Issues and Boards.
Stacks and merges
There is no separate panel for merging: the rows say it. Each row's chip shows where a stacked session or its pull request stands, rows in Merge in order show their place in the list, and while a merge runs, a progress strip in the project's context bar — GitHub is merging 2, Merging 1 of 3 — shows how far it has got; click it to open the session it's working on. Clicking any row opens that session, with its Stack panel when it is stacked or in Merge in order. See Merging.
The workspace dashboard
Click a workspace's row and the right pane shows the workspace view: a Dashboard tab that is this same global table pinned to that workspace — the workspace filter is set for you and hidden, and the summary counts cover that workspace's sessions only, the way the project dashboard's cover one project — followed by a tab for every tool attached to the workspace, and the same Settings button, which opens the workspace's settings on its Toolchain page. The workspace's ⋯ menu gains Open for the same view; the chevron only collapses and expands, as before.
Empty state
Before you've created any sessions, the dashboard shows a centered No sessions yet message explaining that sessions from across your workspaces and projects appear here with live activity and PR state. Your first session shows up automatically once you create it.
Adding repositories
Projects come from the navigation tree, not the dashboard table: hover a workspace, open its ⋯ menu, and choose Add repository… (empty workspaces show an inline + Add repository). You can add a project from a local folder, by searching a connected GitHub or Bitbucket account and cloning a repository, or by cloning a git URL — the two clone flows show a live progress bar and register the result as a project. See Add a repository for the full walkthrough.
Related
- Getting started — add your first repository and run a session
- Status & indicators — what the activity dots and PR badges mean
- Multiple windows — the dashboard, a session or a project in a window of its own
- Keyboard shortcuts — the full shortcut reference