Running Claude Code across several Claude Desktop accounts? Zensu Session Hub is a Mac app that lists the sessions from all of them in one place, opens the right one in one click, and shows which session is keeping your Mac busy. Back in flow.
Session Hub signs in with a Zensu account, and Zensu is in closed beta.
No Zensu account yet? Request workspace access to join the waitlist, and mention Session Hub in the form’s optional “What would you build with Zensu?” field. The Mac app itself is available.
macOS 14 or later · Claude Desktop · Up to 20 accounts
With sound, muted until you turn it on · 1:05. Illustrative interface and fictional data. Move scenes: feature demonstration · simulated handover. Read the film as text
Multiple Claude instances. Dozens of sessions. Somewhere, one of them is waiting for you.
Session Hub lists the Claude Code sessions from all your Claude Desktop accounts in one place. One click opens the session in the correct Claude account: its window comes to the front and flashes a blue outline, so you can see where you landed.
Needs input, Unread response, Completed, PR open — the status shows where to look first, and tabs filter the list: All sessions, Needs attention, In progress and Open pull requests. Completed appears when Claude marks a session as completed.
Session Hub works with the Claude windows you’re already signed in to, up to 20 accounts, and brings the matching one to the front.
Jump to the next session you haven’t opened yet without switching to Session Hub first. Session Hub has to stay running with its window open — behind other apps, hidden or minimized is fine.
History takes you back to the sessions you opened through Session Hub.
Compare CPU and memory across accounts, then per session — including subprocesses — then down to the processes behind it.
Compare CPU and memory across all your accounts at a glance.
CPU and memory for each session, including its subprocesses. Session Hub samples every 2 seconds and keeps up to 30 minutes of history while it runs.
What belongs to this session? Claude Code, tests and builds, and the other helpers it started. Then every process behind it: end a stuck tool or test process, always after a confirmation. Claude’s own processes are never ended from here.
The top bar keeps a 10-minute CPU and memory trend of all Claude processes. The film’s interface, names and numbers are illustrative.
Focus pins the sessions and projects that matter, across accounts. Saved filters bring a whole view back whenever you need it.
Turn on Focus only and the list shows just your focused sessions and projects, while the urgency counters keep counting everything.
Snooze a session until later, and it comes back when the snooze is due. With notifications on, a focused session tells you when it needs input or has finished.
A saved filter keeps statuses, projects, search, text conditions, sort and grouping. Choosing it from the star applies all of it at once, and you can keep up to 20.
Group by project or account. Sort by attention, activity or quota reset.
Feature demonstration · simulated handover Move is shown here as a feature demonstration with a simulated handover.
See every account’s 5-hour and weekly usage, and which sessions are waiting for quota. When an account is full, Move is designed to hand the running session to an account with capacity, using the Zensu plugin for Claude Code.
Session Hub is not a product of Anthropic and is not supported, reviewed or approved by Anthropic. Anthropic’s terms govern the use of Claude. They restrict access to Claude through automated means. On your instruction, Session Hub operates Claude Desktop automatically, for example when it creates, moves or renames sessions or signs you in automatically. Anthropic could regard this as automated access and restrict or suspend your Claude account. You decide which functions you use. Read the Session Hub license terms
Check every account’s 5-hour and weekly usage in one place. A session stopped by a limit moves into Waiting for quota, with its expected availability once the reset time is known. Reading limits briefly brings Claude windows to the front.
Each destination shows its 5-hour and weekly usage, how much is free and its session count; the ones the recommendation favors are marked Recommended. Move here is designed to hand the running session over through the Zensu plugin for Claude Code.
New session recommends an account — Use before reset or Largest reserve — based on quota percentages, not token counts.
Session Hub works with the Claude Desktop windows you’re already signed in to. Here’s what it asks of your Mac, what it keeps there, and where it stops.
Signing in and renewing the license go through your Zensu account, online, over HTTPS. Update checks fetch release information from GitHub.
For the license, Zensu processes your Zensu account and entitlement, a device ID, device name and public device key for each activated Mac, events such as a trial start or a device activation, your acceptance of the license terms, and connection data such as your IP address. Privacy policy, section 3.6
The app itself comes in 9 languages, follows Light, Dark or System, and zooms from 50% to 200%.
Session Hub is available for Claude Desktop on Mac. It signs in with a Zensu account, and Zensu is in closed beta — if you don’t have an account yet, request access now.
Request workspace access takes you to the waitlist form for a closed-beta Zensu account. Mention Session Hub in its optional “What would you build with Zensu?” field.
The app is licensed under the Session Hub license terms.
Everything the 65-second film shows, scene by scene. Lines in quotes appear on screen; the picture is described in square brackets. The film has sound, muted until you turn it on. Its interface and data are illustrative, names and addresses are fictional, and the Move scenes are a feature demonstration with a simulated handover.
Back to the film[A person sits at a desk in front of a large monitor, chin resting on one hand.]
“Your AI is working.”
“Your attention is everywhere.”
[Four Claude Desktop windows, labelled Studio, Build, Research and Review, fill the screen, each with a long list of sessions.]
“Multiple Claude instances. Dozens of sessions.”
[A notice appears in one window: “Your review is needed.”]
“Notifications piling up.”
[Apple’s Activity Monitor: a node process leads the CPU list at 227.8%, and on the Memory tab it uses 7.06 GB.]
“CPU climbs. Memory fills up.”
[The person at the desk, watching the screen.]
[The Session Hub window lists sessions from several projects and accounts.]
“All your sessions. One clear view.”
“Click a session. Go straight to it.”
[Four sessions, each with project, account and status: Review checkout flow, Needs input; Review onboarding guide, Unread response; Audit keyboard navigation, Completed; Update API examples, PR open #42. The pointer selects Review checkout flow.]
“Review checkout flow · studio@example.com”
“Right instance. Right session.”
[The matching Claude window, Studio, comes to the front with Review checkout flow open. The session reads “The review is ready. Which payment behavior should we keep?” and shows Needs your input. Small print: “Illustrative Claude window · Fictional session”.]
“The matching Claude window comes to the front. Your selected session is ready.”
“Find the account behind the load.”
[A Compare accounts table lists three accounts with CPU in cores, memory in GiB and session counts; the build account leads with 3.86 cores and 11.89 GiB.]
“Compare CPU and memory across accounts.”
“Then find the session.”
[CPU by session ranks three sessions; Run integration tests leads at 268.0%.]
“Run integration tests · the heaviest session”
“CPU and memory. Per session.”
[Session resources for Run integration tests: CPU 268.0%, or 2.68 cores, and a memory footprint of 8.40 GiB including subprocesses.]
“268% CPU · 8.40 GiB · including subprocesses”
“Follow the CPU history.”
[A five-minute CPU history climbs and levels off near 270%.]
“See what is behind it.”
[What belongs to this session? Claude Code 860 MiB, Tests & build 7,225 MiB, MCP & other 516 MiB. The process list starts with vitest · integration suite at 227.8% CPU, followed by Session runtime and Language server.]
“vitest · integration suite · 7,225 MiB”
[The person at the desk, watching the screen.]
“Pin the work that matters.”
[Two sessions are pinned into a Focus group at the top of the list.]
“Pin sessions from different projects and accounts.”
“Two priorities. One focused view.”
[Only the Focus group remains: Review checkout flow from Northstar Commerce on Account 01, marked Needs input, and Review onboarding guide from Atlas Docs on Account 03, marked Unread response.]
“Northstar Commerce + Atlas Docs”
“Across two different accounts.”
“8 sessions → 2 priorities”
[The person types at the keyboard.]
“Order the chaos.”
“Search by text.”
[Review is typed into the search field, and the list narrows to two matching results.]
“8 sessions → 2 matching results”
“Choose your project.”
[The project filter is set to Northstar Commerce.]
“Save your filter.”
[The filter is saved as Northstar reviews.]
“Return in one click.”
[The Saved filters menu lists Northstar reviews.]
“Text + project filters. Saved for quick access.”
“Account limit reached?”
[The account build@example.com has used 100% of its 5-hour window and 82% of its week; a session in that account is marked Limit reached.]
“100% used”
“build@example.com”
“Waiting for quota”
“Use Move. Keep going.”
[The session offers Move, Check limits and Mark as done; Move is highlighted.]
“Move this session →”
“The account is full. Your work can continue.”
[Small print: “Feature demonstration · simulated handover”.]
“Choose an account with capacity.”
[A destination card marked Recommended for research@example.com: 5 hours at 24% used, 76% free, resetting in about 59 min; Week · all models at 31% used, 69% free; a Move here button.]
“76% free. Room to continue.”
“76% free in the 5-hour window.”
[Small print: “Feature demonstration · simulated handover”.]
[The person at the desk; the title “Zensu Session Hub” fades in.]
[End card with the Zensu logo.]
“Zensu Session Hub”
“Back in flow.”
“For Claude Desktop on Mac.”
“More integrations planned.”
“Follow for updates”
