Works with your forge.

via the GitHub CLI (gh)

The reference implementation. The whole GitHub loop lives in the app, and GitHub Enterprise works the same once gh is signed in to your host.

• + The full PR lifecycle — review, comment, label, assign, request reviewers, approve, edit, and merge (merge / squash / rebase)
• + A GitHub Actions cockpit — runs, jobs and steps, re-run all or failed, cancel, dispatch a workflow, and read failed-step logs
• + Issues with types, sub-issues, dependencies and linked PRs — plus Discussions
• + Admin: repo settings, collaborators & invitations, branch rulesets, code security toggles, secrets & variables, Pages, webhooks, and a danger zone
• + Insights: 14-day traffic, community health, and a dependencies card

Good to know — Requires gh installed and authenticated. Switch the active account per host in Settings → Accounts.

with an Atlassian API token

Connect with an Atlassian API token (Settings → Accounts), then browse and clone your repositories and work pull requests and Pipelines in the same panels.

• + Pull requests — comment (edit/delete your own), decline, merge (merge / squash / fast-forward, optionally deleting the source branch), edit, and create (drafts included, reviewers pickable at create time)
• + Approve/unapprove, request changes (a true toggle), pick reviewers, and flip draft ↔ ready either way
• + A PR Tasks checklist — add, edit, resolve/unresolve, and delete, with a progress bar and an open-tasks header chip
• + Pipelines — rerun, trigger (pick a custom pipeline, with variables), and stop; publish a local repo to Bitbucket
• + Repo settings — General, default reviewers, branch restrictions, pipeline variables & schedules, deployment environments, webhooks, and a Danger zone

Good to know — Build statuses link out (name, state, URL — no fetchable logs). Reopening a declined PR isn't available (a Bitbucket platform limit), and Bitbucket has no native issue tracker — link a Jira project instead (below).

with an Atlassian API token

Link a Jira Cloud site and project to any repository — from the repo menu or the command palette — and its Issues tab gains a Jira section. Connect with an Atlassian API token, or reuse an existing Bitbucket credential.

Especially handy for Bitbucket, whose native tracker Atlassian retires on 2026-08-20.

• ◆ Browse and filter issues (open / closed / all), and read status, type, priority, assignee, labels, a Markdown description, and comments
• ◆ Agile fields when the project uses them — story points, sprint, a clickable epic / parent, components, and fix versions — discovered automatically per site
• ◆ Create, comment in Markdown, assign, set a due date, change priority, edit labels, and close/reopen along the project's own workflow
• ◆ Edit or delete your own comments — and every action is gated on your Jira permissions, so what you can't do simply doesn't appear
• ◆ Issue keys in your branch, commits, and PR titles are linked back to the Issues tab; a local issue can be promoted to Jira

And for agents — a connected MCP client gets jira_* tools to list and read the linked project, and (behind the remote-write opt-in) comment, create, assign, and update issues.