[{"data":1,"prerenderedAt":227},["ShallowReactive",2],{"site-nav-marketing":3,"feature-git-and-issues":36,"features-all-nav":210},{"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":109,"draft":110,"extension":111,"faq":112,"hero":128,"meta":131,"navTitle":15,"navigation":132,"order":133,"path":16,"sections":134,"seo":206,"slug":207,"stem":208,"__hash__":209},"features\u002Ffeatures\u002Fgit-and-issues.md","Git client, PRs and GitHub issues for AI agents",{"type":40,"value":41,"toc":104},"minimark",[42,47],[43,44,46],"h2",{"id":45},"read-more","Read more",[48,49,50,59,66,73,90,97],"ul",{},[51,52,53,58],"li",{},[54,55,57],"a",{"href":56},"\u002Fdocs\u002Fgit","Git workflow",": the session Git tab",[51,60,61,65],{},[54,62,64],{"href":63},"\u002Fdocs\u002Fproject-git","Project Git client",": the commit graph, remotes, fetching and conflicts",[51,67,68,72],{},[54,69,71],{"href":70},"\u002Fdocs\u002Fpull-requests","Pull requests",": creating them and tracking status and CI",[51,74,75,79,80,84,85,89],{},[54,76,78],{"href":77},"\u002Fdocs\u002Fissues","Issues",", ",[54,81,83],{"href":82},"\u002Fdocs\u002Fboards","Boards"," and ",[54,86,88],{"href":87},"\u002Fdocs\u002Ftoolchain","the Toolchain",": attaching GitHub trackers",[51,91,92,96],{},[54,93,95],{"href":94},"\u002Fdocs\u002Fplnnrly","Plnnrly",": connecting an organization and working its projects",[51,98,99,103],{},[54,100,102],{"href":101},"\u002Fdocs\u002Fbilling","Plans, seats and billing",": what a plan unlocks",{"title":105,"searchDepth":106,"depth":106,"links":107},"",2,[108],{"id":45,"depth":106,"text":46},"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.",false,"md",[113,116,119,122,125],{"question":114,"answer":115},"Do I need the GitHub CLI?","No. Connect GitHub or Bitbucket from Settings → Git ▸ Providers with a one-click sign-in in your browser. Plexus talks to the provider directly from your machine.",{"question":117,"answer":118},"Does Plexus ever force-push?","Not without a lease. The session Git tab's Push is always a normal push: if you rebased or squashed after pushing, git rejects it. The project Git client then offers a Force push confirmation, and a stacked session's branch is pushed again after Plexus syncs it. Both use a lease, so the push fails rather than overwrite a commit someone else pushed in the meantime.",{"question":120,"answer":121},"Which parts need a paid plan?","The Issues tab, the Board tab, the Plnnrly tab, and the issue sidebar in a session. The git clients, pull requests, connecting Plnnrly, attaching trackers, the link between a session and an issue, and the Closes #123 line are free.",{"question":123,"answer":124},"Does Plexus support Bitbucket issues?","Not yet. Bitbucket pull requests are supported. The Issues and Board tabs work with GitHub.",{"question":126,"answer":127},"Do my issues pass through Plexus servers?","No. The Issues and Board tabs talk to GitHub from your machine with the account you connected, and the Plnnrly tab talks to your Plnnrly organization the same way. None of that data reaches us.",{"eyebrow":15,"headline":129,"lead":130},"Git, pull requests and issues, next to the agents.","A git client for each session and one for the repository, pull requests on GitHub and Bitbucket with CI status, and your GitHub issues and project boards in the same window. The git client and pull requests are free. The issue list and boards need a paid plan.",{},true,4,[135,144,159,170,181,192,202],{"id":136,"heading":137,"body":138,"state":139,"docsPath":56,"sim":140},"session-git","A git client for every session","The session's Git tab shows the branch's commits with a divider at the merge-base, a staging panel with discard, stash and an AI-drafted commit message, and Push. Push is never a force-push. Rebase onto the base, merge the base in, or squash the branch with shortcuts that take two modifier keys, because they rewrite history.","working",{"view":141,"tab":142,"anchors":143},"sessions","git",[136],{"id":145,"heading":146,"body":147,"state":148,"docsPath":63,"sim":149},"project-git","The whole repository as a graph","Click a project to open its Git client on the main checkout. The commit graph takes the whole tab and draws every branch as a coloured lane, with author avatars on the commits and branch and tag labels at the side. A branch a session is working on shows that session's state at its tip, Working or Needs you, and a commit an agent makes slides in at the top, highlighted until you look at it. Click a commit and its details slide in as a layer over the graph. The rail on the left opens the references: local branches, each remote, worktrees, stashes, tags and pull requests. Drag one branch label onto another to merge, rebase, fast-forward, push or open a pull request. Conflicts from a merge, rebase, pull or stash pop are resolved in the same tab.","neutral",{"view":150,"project":151,"anchors":152,"note":158},"projectGit","storefront",[153,154,155,156,157],"git-graph","git-refs","git-ref:plexus\u002Fcheckout-flow","git-session:checkout-flow","git-merge","Suggested crop: {x:318,y:130,w:730,h:520}.",{"id":160,"heading":161,"body":162,"state":148,"docsPath":163,"sim":164},"sync","Pull, push and background fetch","The toolbar has the branch switcher, Undo and Redo, Pull, Push and stash, and shows when the project was last fetched. Plexus fetches in the background, about once a minute for the project you are looking at and every ten minutes for the rest. A fetch only downloads: it never merges, checks out or deletes anything, and it pauses while the window is hidden.","\u002Fdocs\u002Fproject-git#automatic-fetching",{"view":150,"project":151,"anchors":165},[166,167,168,169],"git-toolbar","git-branch","git-pull","git-push",{"id":171,"heading":172,"body":173,"state":174,"docsPath":70,"sim":175},"pull-requests","Pull requests on GitHub and Bitbucket","Create PR on a session pushes the branch and opens the pull request. If the worktree has uncommitted changes, Plexus offers to commit them first. An AI-drafted title and description are optional. The branch icon on the session turns green when the pull request is open and purple when it is merged, and its tooltip shows CI status. Connecting GitHub or Bitbucket is a one-click sign-in. You do not need the gh CLI, and the token is kept in your OS keychain.","merged",{"view":141,"anchors":176,"note":180},[177,178,179],"create-pr","row:pricing-page-copy","row:changelog-popup","The hero opens its PR around t=19 (pr event); changelog-popup shows a merged PR.",{"id":182,"heading":183,"body":184,"state":185,"docsPath":77,"sim":186},"issues","GitHub issues, inside the project","Attach a GitHub repository to a project and its Issues tab lists the open issues with GitHub's own filters. Open an issue to edit the title, text, labels, assignees and milestone, or to comment. Start session turns an issue into a session on a branch named after it, sends the issue to the agent as the first prompt, and starts the pull request description with Closes #123. Everything goes from your machine to GitHub with your own account. The tab needs a paid plan. Attaching the repository and the issue link on a session are free.","needs-you",{"view":182,"project":151,"anchors":187,"note":191},[188,189,190],"issues-toolbar","issues-list","issue-start","For the detail view use issue: 142 and anchors issue-detail, issue-start-detail.",{"id":193,"heading":194,"body":195,"state":148,"docsPath":82,"sim":196},"boards","GitHub Projects boards","Attach a GitHub project and its views open in a Board tab: board views as columns, table and roadmap views as tables. Drag a card to another column and the field changes on GitHub. Click a card to open the issue behind it, or start a session from it. The Board tab needs the same paid plan as the Issues tab.",{"view":197,"project":151,"anchors":198,"note":201},"board",[199,197,200],"board-views","board-column:in-progress","Suggested crop: {x:318,y:130,w:1122,h:560}.",{"id":203,"heading":204,"body":205,"state":148,"docsPath":94},"plnnrly","Plnnrly work items, boards and sprints","Connect a Plnnrly organization in Settings → Integrations by signing in through your browser, and attach one of its projects. Its tab has Plnnrly's own views: Backlog, Active sprint and All work, or Board and All work for a project without sprints. Open a work item to edit it and comment. The status menu and the board offer only the moves the project's workflow allows. Start and complete sprints, and start a session from any work item. Everything goes from your machine to your Plnnrly organization. The tab needs the same paid plan as the Issues tab.",{"title":38,"description":109},"git-and-issues","features\u002Fgit-and-issues","hQl3J6Sx0WXNxYmt2cYqffiXyMezfVx6SQUW5AwHGHI",[211,214,217,220,221,224],{"path":7,"title":212,"navTitle":6,"description":213},"Parallel Claude Code sessions with live status","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.",{"path":10,"title":215,"navTitle":9,"description":216},"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":218,"navTitle":12,"description":219},"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":38,"navTitle":15,"description":109},{"path":19,"title":222,"navTitle":18,"description":223},"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":225,"navTitle":21,"description":226},"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.",1792695507495]