[{"data":1,"prerenderedAt":1141},["ShallowReactive",2],{"docs-\u002Fdocs\u002Forg-prompts":3,"docs-nav":857,"docs-updated":1099,"site-nav-marketing":1109},{"id":4,"title":5,"body":6,"description":846,"extension":847,"group":848,"icon":104,"meta":849,"navTitle":850,"navigation":851,"order":852,"path":853,"seo":854,"stem":855,"__hash__":856},"docs\u002Fdocs\u002Forg-prompts.md","Prompts your organization publishes",{"type":7,"value":8,"toc":828},"minimark",[9,24,47,71,76,95,114,121,140,144,164,175,179,189,308,319,331,335,351,374,389,393,447,462,465,470,486,532,536,554,580,591,595,621,638,642,645,671,682,685,689,695,698,724,755,758,762,784,788],[10,11,12,13,18,19,23],"p",{},"Organization prompts let an ",[14,15,17],"a",{"href":16},"\u002Fdocs\u002Faccount#organizations","organization"," publish a ",[14,20,22],{"href":21},"\u002Fdocs\u002Fprompts","prompt template"," once so that every member holding a seat finds it in their own template list, on every machine they sign in on — beside their own templates, badged with the organization's name, and updated for everybody the moment the organization publishes a new revision.",[10,25,26,27,31,32,36,37,41,42,46],{},"It is the fifth thing a ",[14,28,30],{"href":29},"\u002Fdocs\u002Fbilling","plan"," unlocks, and the third one that reaches across a team rather than across your own machines. Like ",[14,33,35],{"href":34},"\u002Fdocs\u002Fshared-workspaces","shared workspaces"," and ",[14,38,40],{"href":39},"\u002Fdocs\u002Fmanaged-settings","managed settings"," it needs a ",[43,44,45],"strong",{},"seat",", and like them it is something somebody else can put on your machine — this time text that ends up in the box you send to your agent, which is why this page spends most of its words on what an organization prompt can and cannot do there.",[48,49,51],"callout",{"tone":50},"warn",[10,52,53,56,57,61,62,65,66,70],{},[43,54,55],{},"A seat, not just membership."," Being in an organization is not enough. Its plan has to include organization prompts ",[58,59,60],"em",{},"and"," you have to hold one of the seats it pays for. Without one you are a full member in every other way — the app is identical, and nothing you have made is touched — you simply are not handed the organization's prompts. A seat is somebody else's to give, so the app says ",[58,63,64],{},"\"This comes with a seat on an organization. Ask whoever administers yours.\""," rather than offering you a checkout page. See ",[14,67,69],{"href":68},"\u002Fdocs\u002Fbilling#seats","Plans, seats and billing",".",[72,73,75],"h2",{"id":74},"what-one-is-once-it-reaches-you","What one is, once it reaches you",[10,77,78,79,82,83,86,87,90,91,94],{},"An organization prompt is an ordinary row in your template list. It is not a separate list you have to consult: it appears in the ",[43,80,81],{},"Template"," field of ",[43,84,85],{},"New session"," and under ",[43,88,89],{},"Insert prompt"," in the Agent tab exactly where your own templates do, you fill in its fields the same way, and the rendered prompt lands in the terminal the same way — typed and ",[43,92,93],{},"left there"," for you to read and send yourself. Plexus never presses return for an organization's prompt any more than it does for yours.",[10,96,97,98,101,102,105,106,109,110,113],{},"What differs is a badge — ",[43,99,100],{},"Org · Acme"," — and what you can do to the row. You can ",[43,103,104],{},"Copy"," an organization's template into your own library and change the copy; you cannot ",[43,107,108],{},"Edit"," or ",[43,111,112],{},"Delete"," the original from your machine, because it is the organization's, and those two are simply absent on its row rather than greyed.",[10,115,116,117,120],{},"The organization owns exactly one thing about it: ",[43,118,119],{},"the text",", at the revision it has published. What you type into its fields, and the finished prompt, stay on your machine — nothing about how you use an organization's prompt is sent back to the organization, or to us.",[10,122,123,124,127,128,131,132,135,136,139],{},"The whole surface lives in ",[43,125,126],{},"Settings → Organizations",", in the ",[43,129,130],{},"Published prompts"," row. The page shows one organization at a time — pick it from the organization picker at the top — and the row's side panel is about that one: what it has published to this machine with each template's revision number, when the list was last checked, ",[43,133,134],{},"Refresh",", and ",[43,137,138],{},"Manage"," for the administrator half.",[72,141,143],{"id":142},"the-badge-and-two-templates-with-one-name","The badge, and two templates with one name",[10,145,146,147,150,151,150,154,150,157,160,161,163],{},"Every template in the list carries a badge saying where it lives — ",[43,148,149],{},"Just me",", ",[43,152,153],{},"Workspace",[43,155,156],{},"Project",[43,158,159],{},"Repository",", or ",[43,162,100],{}," — and since version 0.21.0 the badge shows in both pickers too, not only on the Prompts page.",[10,165,166,167,170,171,174],{},"That matters because there is ",[43,168,169],{},"no override chain",". If you have a template called \"Review\" and your organization publishes one called \"Review\", you see ",[43,172,173],{},"both",", and the badge is how you tell them apart. An organization's prompt never replaces, hides or wins over one of yours, and one of yours never shadows the organization's; the badge is what makes a shared name harmless rather than a rule about which one counts.",[72,176,178],{"id":177},"what-a-revision-is-publish-roll-back-delete","What a revision is — publish, roll back, delete",[10,180,181,182,185,186,70],{},"An organization's template is a ",[43,183,184],{},"list of numbered revisions and one pointer",". Every proposal is a new revision, and a revision is never edited once it exists; what moves is the pointer to the one that is ",[43,187,188],{},"current",[190,191,192,208],"table",{},[193,194,195],"thead",{},[196,197,198,202,205],"tr",{},[199,200,201],"th",{},"Action",[199,203,204],{},"What it does",[199,206,207],{},"Who may do it",[209,210,211,231,249,266,280,294],"tbody",{},[196,212,213,219,226],{},[214,215,216],"td",{},[43,217,218],{},"Propose",[214,220,221,222,225],{},"Writes a new revision and makes it the template's ",[43,223,224],{},"draft",". On a template that does not exist yet, it creates the template. A newer proposal replaces the draft; the earlier one stays in the revision list, unpublished.",[214,227,228],{},[58,229,230],{},"Propose prompts",[196,232,233,238,244],{},[214,234,235],{},[43,236,237],{},"Publish draft",[214,239,240,241,243],{},"Moves ",[43,242,188],{}," onto the draft. Every seat-holder receives it on their next check.",[214,245,246],{},[58,247,248],{},"Publish prompts",[196,250,251,256,261],{},[214,252,253],{},[43,254,255],{},"Roll back…",[214,257,240,258,260],{},[43,259,188],{}," onto any earlier revision, in one action. It reaches every member the same way a publish does.",[214,262,263],{},[58,264,265],{},"Manage revisions",[196,267,268,273,276],{},[214,269,270],{},[43,271,272],{},"Discard draft",[214,274,275],{},"Drops the draft pointer. The revision stays in the list.",[214,277,278],{},[58,279,265],{},[196,281,282,286,289],{},[214,283,284],{},[43,285,112],{},[214,287,288],{},"Retires the template. It disappears from every member's list on their next check, and its revisions go with it.",[214,290,291],{},[58,292,293],{},"Delete prompts",[196,295,296,301,304],{},[214,297,298],{},[43,299,300],{},"Revisions",[214,302,303],{},"Opens the template's history — every retained revision, who proposed it and when, with the current and the draft marked.",[214,305,306],{},[58,307,230],{},[10,309,310,311,314,315,318],{},"Members receive ",[43,312,313],{},"only the current revision",". A draft is invisible outside the people who manage the library, proposing one wakes nobody's machine, and a template that only ever had a draft never reached anybody. The last ",[43,316,317],{},"20"," superseded revisions of a template are kept so a roll back has somewhere to go; older ones are pruned when a new one is proposed.",[48,320,321],{},[10,322,323,326,327,330],{},[43,324,325],{},"Nothing changes a template under a running session."," The text a session rendered is the text it has: a publish or a roll back changes what the ",[58,328,329],{},"next"," fill-in produces, and never what is already in a terminal.",[72,332,334],{"id":333},"what-an-organization-prompt-may-not-contain","What an organization prompt may not contain",[10,336,337,338,342,343,346,347,350],{},"A rendered prompt is typed into Claude Code's input on your machine, and three things mean something special there: a line starting with ",[339,340,341],"code",{},"!"," runs a shell command, a line starting with ",[339,344,345],{},"\u002F"," runs a slash command, and ",[339,348,349],{},"@path"," attaches a file. Your own templates and the ones a repository commits may use all three — you chose that content. An organization's may not, because an administrator should not be able to run a command or attach a file on a colleague's computer by publishing a prompt.",[10,352,353,354,357,358,109,360,362,363,365,366,369,370,373],{},"So an organization prompt is ",[43,355,356],{},"refused at the moment it is proposed"," if its text, after any leading spaces, starts with ",[339,359,341],{},[339,361,345],{},", or mentions a file as ",[339,364,349],{}," anywhere in it — the refusal says which rule and, for a mention, which line, and never quotes the prompt back. An email address such as ",[339,367,368],{},"dana@example.com"," or a lone ",[339,371,372],{},"@"," is fine. The same check runs again on every publish and every roll back, so a revision written before a rule existed cannot be made current past it.",[10,375,376,377,380,381,109,383,385,386,388],{},"And ",[43,378,379],{},"Plexus strips those from an organization prompt as it types it",", on your machine, whatever the organization's service said: a leading ",[339,382,341],{},[339,384,345],{}," is dropped, and the ",[339,387,372],{}," of a path mention is removed so the path stays as plain text. The place that protects your machine is your machine, not the administrator's screen.",[72,390,392],{"id":391},"setting-them-up","Setting them up",[10,394,395,396,399,400,404,405,150,408,150,410,150,412,36,414,416,417,36,420,423,424,427,428,430,431,36,434,437,438,36,440,442,443,70],{},"Everything below needs a role that grants it. Five permissions sit under ",[43,397,398],{},"Prompt library"," in the ",[14,401,403],{"href":402},"\u002Fdocs\u002Froles","role editor",": ",[58,406,407],{},"Use prompts",[58,409,230],{},[58,411,248],{},[58,413,265],{},[58,415,293],{},". ",[43,418,419],{},"Owner",[43,421,422],{},"Admin"," hold all five by default; ",[43,425,426],{},"Maintainer"," holds all but ",[58,429,293],{},"; ",[43,432,433],{},"Member",[43,435,436],{},"Restricted"," hold ",[58,439,407],{},[58,441,230],{},", so every member can receive the library and suggest a change to it, and a role that should also publish is a ",[14,444,446],{"href":445},"\u002Fdocs\u002Froles#making-your-own","copy with the other boxes ticked",[10,448,449,452,453,455,456,458,459,461],{},[43,450,451],{},"Publishing is a separate act from proposing, on purpose."," ",[58,454,230],{}," lets somebody write a revision; ",[58,457,248],{}," is what puts it on other people's machines; ",[58,460,265],{}," is what moves it back or drops a draft. An organization that wants a wide circle suggesting prompts and a narrow one deciding what goes out ticks the boxes on different roles.",[10,463,464],{},"There are two places to do it, and they are the same library.",[466,467,469],"h3",{"id":468},"in-the-app","In the app",[10,471,472,473,475,476,478,479,481,482,485],{},"Pick the organization on ",[43,474,126],{}," and open its ",[43,477,130],{}," row and press ",[43,480,138],{},". A control you may not use is ",[43,483,484],{},"absent rather than disabled",", so the buttons you see are the ones you can press — and if a stale screen lets a click through, the organization's own service refuses the act with a sentence naming the permission you were missing.",[487,488,489,499,518],"ul",{},[490,491,492,494,495,498],"li",{},[43,493,218],{}," opens the same editor as your own templates, with the scope fixed to the organization: name, description, the prompt with its ",[339,496,497],{},"{{fields}}",", and the fields underneath, with a preview. It is refused in the editor, before anything is sent, if the text breaks one of the three rules above.",[490,500,501,502,150,504,506,507,150,509,36,511,513,514,517],{},"Each template shows its current revision — name, revision number, who published it and when — and its draft, if it has one. ",[43,503,237],{},[43,505,255],{}," (a list of the retained revisions to choose from), ",[43,508,272],{},[43,510,300],{},[43,512,112],{}," do what the table above says; ",[43,515,516],{},"Edit as draft"," opens the current or draft text in the editor as a new proposal.",[490,519,520,523,524,527,528,531],{},[43,521,522],{},"Propose to organization…"," on one of ",[43,525,526],{},"your own"," templates on ",[43,529,530],{},"Settings → Prompts"," starts a proposal from it, prefilled, so a prompt that worked for you is one dialog away from the team. If you are in more than one organization that has the feature, the dialog asks which.",[466,533,535],{"id":534},"on-the-web","On the web",[10,537,538,539,416,541,150,543,150,545,150,547,150,549,36,551,553],{},"The same library is a page in your account panel: open the organization, then ",[43,540,398],{},[43,542,218],{},[43,544,237],{},[43,546,255],{},[43,548,272],{},[43,550,300],{},[43,552,112],{}," do exactly what their app counterparts do, and a proposal that breaks one of the three rules is refused there in the same words.",[10,555,556,557,560,561,564,565,568,569,36,572,575,576,579],{},"The prompt box on the web shows its fields as chips too. Type ",[339,558,559],{},"{{"," (at the start of a line or after a space) to pick one from a list, or open the ",[43,562,563],{},"Merge tags"," panel beside the box, which lists every field in the form, and click or drag one in. An ",[43,566,567],{},"On or off"," field gives you two tags, ",[43,570,571],{},"Show when …",[43,573,574],{},"End …",". Whatever sits between them is sent only when the box is ticked. The list is built from the fields you set up under the prompt, so add a field there first. Unlike in the app, typing a new name does not create a field for you. What is saved is the same plain ",[339,577,578],{},"{{name}}"," text the app writes, so a proposal made on the web opens in the app's editor unchanged, and the other way round.",[10,581,582,583,586,587,590],{},"You get there from ",[43,584,585],{},"Settings → My account → Manage on the web"," in the app, or from the ",[43,588,589],{},"Sign in"," link in this site's header.",[466,592,594],{"id":593},"reaching-the-members","Reaching the members",[10,596,597,598,36,601,604,605,608,609,611,612,614,615,160,618,70],{},"A published revision reaches a member's machine on that machine's next check — the same check that fetches the organization's ",[14,599,35],{"href":600},"\u002Fdocs\u002Fshared-workspaces#staying-up-to-date",[14,602,40],{"href":603},"\u002Fdocs\u002Fmanaged-settings#reaching-the-members",": when Plexus starts, when you switch back to its window, a couple of seconds after you change something, and on the schedule set by ",[43,606,607],{},"Check for changes every (minutes)"," on the Sync page. ",[43,610,134],{}," under ",[43,613,130],{}," asks immediately, and the list carries its own clock per organization — ",[58,616,617],{},"Checked 4 minutes ago",[58,619,620],{},"Not checked yet",[10,622,623,624,627,628,631,632,634,635,637],{},"That check does ",[43,625,626],{},"not"," require ",[43,629,630],{},"Sync this machine"," to be on. An organization prompt is text arriving from your organization, not anything of yours leaving, so it needs only that you are signed in, hold a seat, the organization's plan includes it, and your role grants ",[58,633,407],{}," — which every role you start with does. A role that denies ",[58,636,407],{}," receives nothing, and the app clears that organization's prompts from the machine when the organization says so.",[72,639,641],{"id":640},"offline-lapses-and-leaving","Offline, lapses and leaving",[10,643,644],{},"The prompts your organization publishes are held on your machine, and the app lists and renders them from there — never from a live connection. So the rule for every kind of trouble is the same one.",[48,646,647],{},[10,648,649,652,653,655,656,658,659,662,663,666,667,670],{},[43,650,651],{},"What arrived stays, read-only."," Offline, on a machine that cannot reach us, on a plan that has lapsed, or after your seat was taken back: nothing disappears. Every organization prompt already on the machine keeps listing and running at the revision it last received, and that organization's ",[43,654,130],{}," row on ",[43,657,126],{}," says plainly that the list may be stale — ",[58,660,661],{},"\"We haven't been able to check your plan\"",", with ",[43,664,665],{},"Check again"," beside it — while listing, below a separator, what this machine still holds. What a lapse costs is the ",[58,668,669],{},"next revision",", not the prompt you already have.",[10,672,673,674,677,678,681],{},"An organization's prompts are dropped from a machine in exactly two cases, and both are a definite answer from the organization rather than a failed one: ",[43,675,676],{},"the organization confirms you are no longer in it"," — you left, or you were removed — or ",[43,679,680],{},"it says your role may no longer use its prompts",". On the next successful check that organization's prompts go, your own templates are untouched, and no other organization's prompts are affected. A check that failed, timed out or was refused for want of a plan never drops anything.",[10,683,684],{},"Deleting one is never blocked. An administrator can delete a template and discard a draft on a plan that has lapsed, with too few seats, or with the organization's plan no longer covering organization prompts at all, and the app shows those two controls under the stale panel for exactly that reason — see below.",[72,686,688],{"id":687},"what-needs-a-seat-and-what-never-stops","What needs a seat, and what never stops",[10,690,691,694],{},[43,692,693],{},"A seat is what buys the receiving."," Being handed a revision, and every part of proposing, publishing and rolling back, need the organization's plan to cover organization prompts and you to hold one of its seats. Rolling back needs it too, because a roll back changes what every member holds just as a publish does.",[10,696,697],{},"Three things carry on regardless, and each is deliberate:",[487,699,700,706,718],{},[490,701,702,705],{},[43,703,704],{},"What already arrived."," A prompt your machine already holds keeps listing and running — see the callout above.",[490,707,708,711,712,714,715,717],{},[43,709,710],{},"Taking something back."," An administrator can still ",[43,713,112],{}," a template and ",[43,716,272],{}," after a plan lapses, with a seat shortfall, and on a plan that no longer includes the feature. Otherwise a lapsed organization could not withdraw a prompt it no longer stood behind from a departed colleague's machine, which is exactly backwards.",[490,719,720,723],{},[43,721,722],{},"Your own library."," Nothing an organization publishes, rolls back or deletes touches a template of yours, and nothing about a lapse or a seat does either.",[10,725,726,727,730,731,734,735,36,737,739,740,150,742,36,744,746,747,750,751,754],{},"If more seats are handed out than the plan pays for, the admin panel shows a warning naming both numbers and ",[43,728,729],{},"proposing and publishing pause until it is fixed"," — the same rule as for ",[14,732,35],{"href":733},"\u002Fdocs\u002Fshared-workspaces#if-more-seats-are-handed-out-than-the-plan-pays-for",". In the app ",[43,736,218],{},[43,738,237],{}," are absent while it lasts; on the web they are disabled. ",[43,741,255],{},[43,743,272],{},[43,745,112],{}," stay. Press ",[43,748,749],{},"Manage seats"," on the banner — it opens the organization's ",[43,752,753],{},"Plan, seats and people"," row on the same page — or add seats, and it clears itself.",[10,756,757],{},"And nothing local is affected by any of it. Sessions, worktrees, the agent terminal, review, the explorer, the git client, hooks, pull requests and the dashboard are identical with a seat and without one, and always will be.",[72,759,761],{"id":760},"what-sync-does-and-does-not-carry","What sync does and does not carry",[10,763,764,36,768,772,773,776,777,779,780,783],{},[14,765,767],{"href":766},"\u002Fdocs\u002Fsync","Cross-device sync",[14,769,771],{"href":770},"\u002Fdocs\u002Fprompts#keeping-them-on-every-machine","your own prompt library"," carry ",[58,774,775],{},"your"," templates between ",[58,778,775],{}," machines. An organization's prompts are ",[43,781,782],{},"not part of either",": each of your machines receives them from the organization directly, on the check described above, and turning sync off does not stop them arriving. They are never written into your account, never appear in the preview of what this machine sends, and are not counted in the numbers on the Prompts page — and a template of yours reaches the organization's library in exactly one way, by your proposing it there yourself.",[72,785,787],{"id":786},"related","Related",[487,789,790,796,805,811,816,821],{},[490,791,792,795],{},[14,793,794],{"href":21},"Prompt templates"," — writing one, its fields, and where your own templates live.",[490,797,798,36,801,804],{},[14,799,800],{"href":34},"Shared workspaces",[14,802,803],{"href":39},"Managed settings"," — the other two things an organization hands its members, on the same page in the app.",[490,806,807,810],{},[14,808,809],{"href":402},"Roles and permissions"," — the five prompt permissions and who holds them.",[490,812,813,815],{},[14,814,69],{"href":68}," — what a seat is, and how one is given.",[490,817,818,820],{},[14,819,767],{"href":766}," — why an organization's prompts are not part of it.",[490,822,823,827],{},[14,824,826],{"href":825},"\u002Flegal\u002Fprivacy","Privacy Policy"," — the field-by-field account of what an organization's library holds and what never leaves your machine for it.",{"title":829,"searchDepth":830,"depth":830,"links":831},"",2,[832,833,834,835,836,842,843,844,845],{"id":74,"depth":830,"text":75},{"id":142,"depth":830,"text":143},{"id":177,"depth":830,"text":178},{"id":333,"depth":830,"text":334},{"id":391,"depth":830,"text":392,"children":837},[838,840,841],{"id":468,"depth":839,"text":469},3,{"id":534,"depth":839,"text":535},{"id":593,"depth":839,"text":594},{"id":640,"depth":830,"text":641},{"id":687,"depth":830,"text":688},{"id":760,"depth":830,"text":761},{"id":786,"depth":830,"text":787},"Publish Claude Code prompt templates to every member of a Plexus organization as numbered revisions: proposing, publishing, rolling back, limits and seats.","md","Integrations",{},"Organization prompts",true,47,"\u002Fdocs\u002Forg-prompts",{"title":5,"description":846},"docs\u002Forg-prompts","d1E4pvptmsqAys6F4It-5zn4nMFfoGF_Fucc5VCoxYE",[858,865,871,876,882,889,895,902,909,916,924,931,938,945,952,959,965,972,976,982,988,996,1003,1009,1013,1020,1027,1032,1037,1042,1046,1050,1051,1058,1065,1072,1079,1085,1092],{"path":859,"title":860,"navTitle":860,"description":861,"icon":862,"group":863,"order":864},"\u002Fdocs","Introduction","Plexus 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.","BookOpen","Overview",1,{"path":866,"title":867,"navTitle":868,"description":869,"icon":870,"group":863,"order":830},"\u002Fdocs\u002Finstall","Installation","Install","Download and install Plexus on macOS (Apple Silicon or Intel), Linux (.deb or AppImage) or Windows, check Claude Code and Git, and get automatic updates.","Download",{"path":872,"title":873,"navTitle":873,"description":874,"icon":875,"group":863,"order":839},"\u002Fdocs\u002Frequirements","Requirements","What Plexus needs on your machine: the Claude Code CLI and Git, plus optional GitHub or Bitbucket access, notify-send on Linux, and supported platforms.","Check",{"path":877,"title":878,"navTitle":878,"description":879,"icon":880,"group":863,"order":881},"\u002Fdocs\u002Fgetting-started","Getting started","Your first run of Plexus: add a git repository, create a session in its own worktree, start Claude Code and send your first prompt.","Rocket",4,{"path":883,"title":884,"navTitle":885,"description":886,"icon":887,"group":863,"order":888},"\u002Fdocs\u002Fconcepts","Core concepts","Concepts","Workspaces, projects and sessions in Plexus — each session usually its own git worktree running Claude Code — and the two status indicators on every row.","Boxes",5,{"path":890,"title":891,"navTitle":891,"description":892,"icon":893,"group":863,"order":894},"\u002Fdocs\u002Farchitecture","Architecture","How 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.","Package",6,{"path":896,"title":897,"navTitle":897,"description":898,"icon":899,"group":900,"order":901},"\u002Fdocs\u002Fdashboard","Dashboard","One live table of every Claude Code session across your Plexus workspaces, with activity state, PR status, summary counts, filters and sorting.","LayoutGrid","Working with projects",10,{"path":903,"title":904,"navTitle":905,"description":906,"icon":907,"group":900,"order":908},"\u002Fdocs\u002Fproject-git","Project Git client","Git GUI","A 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.","GitGraph",11,{"path":910,"title":911,"navTitle":912,"description":913,"icon":914,"group":900,"order":915},"\u002Fdocs\u002Fproject-terminal","Project Terminal","Terminal","Open 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.","MonitorDot",12,{"path":917,"title":918,"navTitle":919,"description":920,"icon":921,"group":922,"order":923},"\u002Fdocs\u002Fsessions","Sessions & worktrees","Sessions","Create 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.","Bot","Working with sessions",20,{"path":925,"title":926,"navTitle":927,"description":928,"icon":929,"group":922,"order":930},"\u002Fdocs\u002Fstatus","Status & notifications","Status","What 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.","Activity",21,{"path":932,"title":933,"navTitle":934,"description":935,"icon":936,"group":922,"order":937},"\u002Fdocs\u002Fagent","The Agent tab","Agent","The Agent tab is the Claude Code terminal in every session: send prompts, paste images, compose multi-line input, rewind, and choose the permission mode.","Sparkles",22,{"path":939,"title":940,"navTitle":941,"description":942,"icon":943,"group":922,"order":944},"\u002Fdocs\u002Fexplorer","Explorer & editor","Explorer","Browse 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.","FileText",23,{"path":946,"title":947,"navTitle":948,"description":949,"icon":950,"group":922,"order":951},"\u002Fdocs\u002Freview","Review & diffs","Review","Review 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.","GitPullRequestArrow",24,{"path":953,"title":954,"navTitle":955,"description":956,"icon":957,"group":922,"order":958},"\u002Fdocs\u002Fgit","Git workflow","Session Git","The 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.","GitMerge",25,{"path":960,"title":961,"navTitle":961,"description":962,"icon":963,"group":922,"order":964},"\u002Fdocs\u002Fpull-requests","Pull requests","Open 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.","Github",26,{"path":966,"title":967,"navTitle":968,"description":969,"icon":970,"group":922,"order":971},"\u002Fdocs\u002Fstacks","Stacks & ordered merging","Stacks & merging","Stack 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.","Layers",27,{"path":973,"title":912,"navTitle":912,"description":974,"icon":914,"group":922,"order":975},"\u002Fdocs\u002Fterminal","Open 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.",28,{"path":977,"title":978,"navTitle":978,"description":979,"icon":980,"group":922,"order":981},"\u002Fdocs\u002Fsplit-view","Split view","Put 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.","Grid2x2",29,{"path":983,"title":984,"navTitle":984,"description":985,"icon":986,"group":922,"order":987},"\u002Fdocs\u002Fwindows","Multiple windows","Open 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.","AppWindow",30,{"path":989,"title":990,"navTitle":991,"description":992,"icon":993,"group":994,"order":995},"\u002Fdocs\u002Fhooks","Lifecycle hooks","Hooks","Run 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.","RefreshCw","Automation",31,{"path":997,"title":998,"navTitle":999,"description":1000,"icon":1001,"group":994,"order":1002},"\u002Fdocs\u002Fworktrees","Worktrees & env files","Worktrees & env","Where 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.","FolderGit2",32,{"path":1004,"title":1005,"navTitle":1005,"description":1006,"icon":1007,"group":994,"order":1008},"\u002Fdocs\u002Fsecrets","Secrets","Plexus keeps secrets in your OS keychain — macOS Keychain, Windows Credential Manager or Linux Secret Service — write-only, and out of every hook it runs.","KeyRound",33,{"path":21,"title":794,"navTitle":1010,"description":1011,"icon":104,"group":994,"order":1012},"Prompts","Save 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.",34,{"path":1014,"title":1015,"navTitle":1016,"description":1017,"icon":1018,"group":848,"order":1019},"\u002Fdocs\u002Fconnections","Connecting a git provider","Git providers","Connect 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.","PlugZap",40,{"path":1021,"title":1022,"navTitle":1023,"description":1024,"icon":1025,"group":848,"order":1026},"\u002Fdocs\u002Faccount","Your Plexus account","Plexus account","Create 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.","UsersRound",41,{"path":29,"title":69,"navTitle":1028,"description":1029,"icon":1030,"group":848,"order":1031},"Billing","What a paid Plexus plan unlocks, individual and per-seat organization plans, buying through Moneybird, invitations, invoices and VAT, and cancelling.","CreditCard",42,{"path":766,"title":767,"navTitle":1033,"description":1034,"icon":1035,"group":848,"order":1036},"Sync","Sync your Plexus settings, workspaces and projects to every machine you sign in on, after a preview of exactly what would leave this one.","Cloud",43,{"path":402,"title":809,"navTitle":1038,"description":1039,"icon":1040,"group":848,"order":1041},"Roles","Control 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.","ShieldCheck",44,{"path":34,"title":800,"navTitle":800,"description":1043,"icon":1044,"group":848,"order":1045},"Set up a workspace once in a Plexus organization so every member gets the same repositories in their sidebar: join modes, leaving, cloning, and seats.","Building2",45,{"path":39,"title":803,"navTitle":803,"description":1047,"icon":1048,"group":848,"order":1049},"Let a Plexus organization recommend, enforce or dry-run settings on members' machines: the three levels, locked rows, eligible settings and offline rules.","Lock",46,{"path":853,"title":5,"navTitle":850,"description":846,"icon":104,"group":848,"order":852},{"path":1052,"title":1053,"navTitle":1054,"description":1055,"icon":1056,"group":848,"order":1057},"\u002Fdocs\u002Fissues","Issues from your tracker","Issues","Read, 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.","CircleDot",48,{"path":1059,"title":1060,"navTitle":1061,"description":1062,"icon":1063,"group":848,"order":1064},"\u002Fdocs\u002Ftoolchain","The Toolchain","Toolchain","Attach 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.","Wrench",49,{"path":1066,"title":1067,"navTitle":1068,"description":1069,"icon":1070,"group":848,"order":1071},"\u002Fdocs\u002Fboards","Boards from GitHub Projects","Boards","Work 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.","SquareKanban",50,{"path":1073,"title":1074,"navTitle":1075,"description":1076,"icon":1077,"group":848,"order":1078},"\u002Fdocs\u002Fplnnrly","Plnnrly work items, boards and sprints","Plnnrly","Connect 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.","ClipboardList",51,{"path":1080,"title":1081,"navTitle":1081,"description":1082,"icon":1081,"group":1083,"order":1084},"\u002Fdocs\u002Fsettings","Settings","Every Plexus setting and its default, and how settings layer from global to workspace, project and session — including organization-enforced values.","Reference",52,{"path":1086,"title":1087,"navTitle":1088,"description":1089,"icon":1090,"group":1083,"order":1091},"\u002Fdocs\u002Fshortcuts","Keyboard shortcuts","Shortcuts","Every 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.","Keyboard",53,{"path":1093,"title":1094,"navTitle":1095,"description":1096,"icon":1097,"group":1083,"order":1098},"\u002Fdocs\u002Ffeedback","Sending feedback","Feedback","Send 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.","SquarePen",54,{"\u002Fdocs\u002Faccount":1100,"\u002Fdocs\u002Fagent":1101,"\u002Fdocs\u002Farchitecture":1101,"\u002Fdocs\u002Fbilling":1100,"\u002Fdocs\u002Fboards":1101,"\u002Fdocs\u002Fconcepts":1102,"\u002Fdocs\u002Fconnections":1103,"\u002Fdocs\u002Fdashboard":1100,"\u002Fdocs\u002Fexplorer":1104,"\u002Fdocs\u002Ffeedback":1102,"\u002Fdocs\u002Fgetting-started":1105,"\u002Fdocs\u002Fgit":1100,"\u002Fdocs\u002Fhooks":1106,"\u002Fdocs":1101,"\u002Fdocs\u002Finstall":1101,"\u002Fdocs\u002Fissues":1102,"\u002Fdocs\u002Fmanaged-settings":1104,"\u002Fdocs\u002Forg-prompts":1104,"\u002Fdocs\u002Fplnnrly":1102,"\u002Fdocs\u002Fproject-git":1103,"\u002Fdocs\u002Fproject-terminal":1107,"\u002Fdocs\u002Fprompts":1106,"\u002Fdocs\u002Fpull-requests":1100,"\u002Fdocs\u002Frequirements":1105,"\u002Fdocs\u002Freview":1104,"\u002Fdocs\u002Froles":1101,"\u002Fdocs\u002Fsecrets":1106,"\u002Fdocs\u002Fsessions":1100,"\u002Fdocs\u002Fsettings":1100,"\u002Fdocs\u002Fshared-workspaces":1104,"\u002Fdocs\u002Fshortcuts":1108,"\u002Fdocs\u002Fsplit-view":1100,"\u002Fdocs\u002Fstacks":1100,"\u002Fdocs\u002Fstatus":1100,"\u002Fdocs\u002Fsync":1100,"\u002Fdocs\u002Fterminal":1107,"\u002Fdocs\u002Ftoolchain":1102,"\u002Fdocs\u002Fwindows":1106,"\u002Fdocs\u002Fworktrees":1106},"2026-10-16","2026-10-06","2026-10-15","2026-10-22","2026-10-09","2026-10-11","2026-10-14","2026-10-13","2026-10-19",{"features":1110,"compare":1128},[1111,1114,1116,1119,1122,1125],{"label":1112,"to":1113},"Sessions & status","\u002Ffeatures\u002Fsessions-and-status",{"label":948,"to":1115},"\u002Ffeatures\u002Freview",{"label":1117,"to":1118},"Worktrees & hooks","\u002Ffeatures\u002Fworktrees-and-hooks",{"label":1120,"to":1121},"Git & issues","\u002Ffeatures\u002Fgit-and-issues",{"label":1123,"to":1124},"Stacks","\u002Ffeatures\u002Fstacks",{"label":1126,"to":1127},"Teams","\u002Ffeatures\u002Fteams",[1129,1132,1135,1138],{"label":1130,"to":1131},"vs Claude Code","\u002Fcompare\u002Fclaude-code",{"label":1133,"to":1134},"vs Claude Squad and Nimbalyst","\u002Fcompare\u002Fclaude-squad-and-nimbalyst",{"label":1136,"to":1137},"vs Conductor","\u002Fcompare\u002Fconductor",{"label":1139,"to":1140},"vs Cursor","\u002Fcompare\u002Fcursor",1792695510104]