[{"data":1,"prerenderedAt":194},["ShallowReactive",2],{"site-nav-marketing":3,"feature-sessions-and-status":36,"features-all-nav":177},{"features":4,"compare":23},[5,8,11,14,17,20],{"label":6,"to":7},"Sessions & status","\u002Ffeatures\u002Fsessions-and-status",{"label":9,"to":10},"Review","\u002Ffeatures\u002Freview",{"label":12,"to":13},"Worktrees & hooks","\u002Ffeatures\u002Fworktrees-and-hooks",{"label":15,"to":16},"Git & issues","\u002Ffeatures\u002Fgit-and-issues",{"label":18,"to":19},"Stacks","\u002Ffeatures\u002Fstacks",{"label":21,"to":22},"Teams","\u002Ffeatures\u002Fteams",[24,27,30,33],{"label":25,"to":26},"vs Claude Code","\u002Fcompare\u002Fclaude-code",{"label":28,"to":29},"vs Claude Squad and Nimbalyst","\u002Fcompare\u002Fclaude-squad-and-nimbalyst",{"label":31,"to":32},"vs Conductor","\u002Fcompare\u002Fconductor",{"label":34,"to":35},"vs Cursor","\u002Fcompare\u002Fcursor",{"id":37,"title":38,"body":39,"description":85,"draft":86,"extension":87,"faq":88,"hero":101,"meta":104,"navTitle":6,"navigation":105,"order":106,"path":7,"sections":107,"seo":173,"slug":174,"stem":175,"__hash__":176},"features\u002Ffeatures\u002Fsessions-and-status.md","Parallel Claude Code sessions with live status",{"type":40,"value":41,"toc":80},"minimark",[42,47],[43,44,46],"h2",{"id":45},"read-more","Read more",[48,49,50,59,66,73],"ul",{},[51,52,53,58],"li",{},[54,55,57],"a",{"href":56},"\u002Fdocs\u002Fconcepts","Concepts",": workspaces, projects and sessions",[51,60,61,65],{},[54,62,64],{"href":63},"\u002Fdocs\u002Fsessions","Sessions & worktrees",": creating, stopping, resuming and archiving sessions",[51,67,68,72],{},[54,69,71],{"href":70},"\u002Fdocs\u002Fstatus","Status & notifications",": what every dot, ring and colour means",[51,74,75,79],{},[54,76,78],{"href":77},"\u002Fdocs\u002Fdashboard","Dashboard",": the global, project and workspace tables",{"title":81,"searchDepth":82,"depth":82,"links":83},"",2,[84],{"id":45,"depth":82,"text":46},"Run many Claude Code agents at once, each in its own git worktree, and see which one needs you: working, needs you, delegating or idle, across every repo.",false,"md",[89,92,95,98],{"question":90,"answer":91},"Do I need an Anthropic API key?","No. Plexus runs the Claude Code CLI you already have installed and passes your existing Claude Code login through to each session. It does not ship its own agent.",{"question":93,"answer":94},"How does Plexus know a session is waiting for me?","When a session starts, Plexus installs a small set of activity hooks in its working directory. Claude Code reports turn ends, questions, permission prompts and plan approvals through them, over a private loopback channel. Every couple of seconds Plexus also checks the dot against Claude Code's own record of what the session is doing, and against the session's transcript, so an Esc interrupt or an approved permission prompt is picked up even though no hook reports it.",{"question":96,"answer":97},"What happens to running sessions when I quit Plexus?","The agent processes end with the app. On the next launch those sessions show as stopped, with their conversation id kept, so Resume reattaches the same conversation.",{"question":99,"answer":100},"The dot is stuck on the wrong colour. What now?","It should correct itself within a few seconds, including after you press Esc or approve a permission prompt. If it stays wrong, reset the status from the session's ⋯ menu. If the dot never moves at all, run Check activity hooks… from the same menu to find out which link is broken.",{"eyebrow":6,"headline":102,"lead":103},"Run five agents. Know which one needs you.","Every session is a Claude Code agent in its own git worktree. A dot on each row says whether it is working, waiting for you or idle, and the dashboard shows every session in one table.",{},true,1,[108,120,131,142,152,162],{"id":109,"heading":110,"body":111,"state":112,"docsPath":56,"sim":113},"tree","One tree for every repository","Plexus arranges your work as workspace, project, session. A workspace groups related repositories, a project is one git repository, and a session is one named Claude Code agent on its own branch. Expand a workspace in the sidebar to see its projects, and a project to see its sessions. Settings and hooks cascade down the same tree, so you set a default once for a group of similar repositories.","neutral",{"view":114,"anchors":115,"note":119},"sessions",[116,109,117,118],"sidebar","project:storefront","row:checkout-flow","Crop to the sidebar ({x:0,y:88,w:318,h:420}) on narrow screens.",{"id":121,"heading":122,"body":123,"state":124,"docsPath":70,"sim":125},"states","Working, Needs you, Idle","A coloured dot sits on every session row. Green and pulsing means the agent is mid-turn. Amber means it is your turn: the turn ended, or the agent stopped on a question, a permission prompt or a plan waiting for approval. Grey means nothing is in flight. The dot follows Claude Code's own lifecycle events, reported back over a private loopback channel, so it reflects what the agent is actually doing. Only the session's own agent moves it.","needs-you",{"view":114,"start":126,"anchors":127,"note":130},6,[118,128,129],"perm-prompt","needs-pill","At t=6 the hero session stops on a permission prompt and the pill reads 2 need you.",{"id":132,"heading":133,"body":134,"state":132,"docsPath":135,"sim":136},"delegating","Background work gets its own signal","When the agent hands work off and carries on without waiting, to background subagents, a workflow, a teammate or a cloud session, a blue ring appears around the dot. The ring combines with all three colours, and a row whose main agent is free while delegated work runs reads Delegating. A workflow keeps the ring lit for its whole run and counts as one item. Hover the dot for what is running, including how many of a workflow's agents are live and any background shell commands, which are listed but do not light the ring. Subagents the agent is waiting on count as ordinary work, so they show as a green dot with no ring.","\u002Fdocs\u002Fstatus#background-work",{"view":114,"start":137,"anchors":138,"note":141},0,[139,140],"row:conpty-teardown","row:settings-service","conpty-teardown is Delegating at t=0; settings-service launches a subagent at t=4.",{"id":143,"heading":144,"body":145,"state":146,"docsPath":77,"sim":147},"dashboard","Every session in one table","Press ⌘0 for the global dashboard: one live table of every session across all workspaces, with its state, project, branch, workspace and pull request badge. The header counts sessions working, waiting and idle, plus open and merged pull requests. The default sort puts sessions that need you first. Click a row to jump to that session. Each project and workspace has the same table, scoped to itself.","working",{"view":143,"anchors":148},[149,150,151],"dash-chips","dash-list","dash-row:checkout-flow",{"id":153,"heading":154,"body":155,"state":124,"docsPath":156,"sim":157},"notifications","Told when it is your turn","When a session starts waiting, Plexus sends a native notification that names the session and what it needs, even with the window minimised. Notifications are on by default. An optional two-note chime, or a sound file of your own, is off by default. While background subagents or a workflow are still running, Plexus waits and tells you once, when that work has finished. Notices that need nothing from you, such as a background agent finishing, do not count as waiting.","\u002Fdocs\u002Fstatus#getting-notified",{"view":114,"start":158,"anchors":159,"note":161},17,[129,160],"row:hook-bridge-retry","The simulation has no OS notification. Show the pill and the row that just turned amber instead.",{"id":163,"heading":164,"body":165,"state":112,"docsPath":166,"sim":167},"lifecycle","Stop, resume, pick up where you left off","Stopping a session ends the agent process and keeps the worktree, the branch and the conversation. Resume restarts the session and reattaches the same conversation. Sessions survive quitting Plexus: running agents come back as stopped, and the next Resume reattaches them. Archive hides a session without deleting anything, and ⌘K finds any session by name, branch, project or workspace.","\u002Fdocs\u002Fsessions#lifecycle",{"view":114,"anchors":168,"note":172},[169,170,171],"row:changelog-popup","search","context","changelog-popup is a stopped session with a merged PR.",{"title":38,"description":85},"sessions-and-status","features\u002Fsessions-and-status","i1hzYEbfAGuFEzKwTDgL0SPr1v7DI76-plKEHHn-Am0",[178,179,182,185,188,191],{"path":7,"title":38,"navTitle":6,"description":85},{"path":10,"title":180,"navTitle":9,"description":181},"Review AI agent changes like a pull request","A PR-style diff of each Claude Code session's worktree, inline comments the agent acts on, AI review, a review-and-fix cycle and the PR conversation.",{"path":13,"title":183,"navTitle":12,"description":184},"A git worktree per agent, set up by your own hooks","Every Claude Code session gets its own git worktree, your .env files, a block of dev-server ports, and your Create, Run and Teardown hooks at three levels.",{"path":16,"title":186,"navTitle":15,"description":187},"Git client, PRs and GitHub issues for AI agents","A git client per Claude Code session and per repo, GitHub and Bitbucket pull requests with CI status, and GitHub Issues and Projects boards in one window.",{"path":19,"title":189,"navTitle":18,"description":190},"Stacked pull requests and ordered merging for Claude Code sessions","Stack Claude Code sessions on each other's branches. Plexus keeps every branch synced as the agents work, shows the stack as a map, and merges it in order, as a GitHub stack or through a merge queue.",{"path":22,"title":192,"navTitle":21,"description":193},"Teams: organizations, managed settings, prompts","Organizations, shared workspaces, managed settings, a shared prompt library and sync for teams on Claude Code. Seats are paid; the core app stays free.",1792695507396]