Pull requests

Open a pull request straight from a session's branch and watch its status — open, merged, or closed, plus CI — without leaving Plexus.

Before you start

PR features need a connected git provider. Open Settings → Git providers and click Connect for GitHub or Bitbucket — a one-click sign-in, no CLI required. Plexus stores the resulting token in your OS keychain and talks to the provider directly from your machine; the token is never sent to us. See Connections.

A session also has to be on a named feature branch with at least one commit beyond its base. Sessions on the project's main branch can't open a PR.

Create a pull request

1. On the session row, open the ⋯ menu and choose Create PR.
2. Fill in the title, an optional description, and an optional base branch.
3. Click Create.

Plexus pushes the branch to origin, opens the PR on your provider (GitHub or Bitbucket), and the session's branch icon turns green.

A dirty worktree

If the worktree has uncommitted changes when you create a PR, Plexus doesn't fail — it shows a commit-then-PR dialog. Enter a commit message (or accept the default WIP on <branch>), and Plexus commits, pushes, and opens the PR in one flow.

Auto-generate the title and description

Turn on git.pr.autoGenerateDescription (default off) to have the agent draft the PR title and description from the diff when the dialog opens. It spends an AI turn, and you can still edit the draft before submitting.

Track PR status

Once a PR exists, the branch icon next to the session reflects its state at a glance:

Hover the icon for details, including the aggregate CI status (pending, passing, or failing) from the provider's checks (GitHub check runs / Bitbucket pipelines). Click a green or purple icon to open the PR in your browser.

Status is polled automatically — when you focus the window, on a periodic refresh, and when the agent finishes a turn. You can also refresh on demand from the session ⋯ menu. CI status updates alongside the PR, so a very fast pipeline may briefly show "pending" until the next refresh. For how the branch and activity indicators relate, see Session status.

After the PR is created

Two optional behaviors keep sessions tidy as PRs progress:

• Auto-rename from PR title — session.autoRenameOnPr (default on) keeps the session name in sync with the PR title. The underlying git branch keeps its original name.
• Auto-teardown on merge — git.teardownOnMerge (default off) tears the session down when Plexus detects its PR has merged. It honors your teardownMode setting, so it archives or deletes per your configuration.

Configure all of these in Settings.