Skip to main content
The Bitbucket toolkit lets agents work with Bitbucket Cloud: list workspaces and repositories, read file content, list branches and commits, and manage pull requests and issues. Authentication is per-user OAuth — each user connects their own Bitbucket account. Add it on the agent Toolkits tab. The first use prompts the user to connect Bitbucket if they have not already.

​
Prerequisites

  • Bitbucket Cloud access to the workspaces and repos the agent should use
  • An agent you can edit
  • Users who will chat with the agent must complete the Bitbucket OAuth connect flow when prompted

​
Setup

  1. Open the agent → Toolkits → add Bitbucket.
  2. Optionally set a default workspace in toolkit config (tools still accept an explicit workspace when needed).
  3. Save the agent. In Chat, connect Bitbucket when prompted (or via the authenticate tool).
  4. @-mention Bitbucket tools in the personality prompt for repo, PR, or issue tasks.

​
Available tools

When the user is not connected, the agent can offer Authenticate Bitbucket to start the OAuth flow.

​
Use cases

  • Summarize open pull requests or recent commits for a repository
  • Read a config or README file from a branch during troubleshooting
  • Open a PR after documenting a change, or file a bug issue from chat
  • Discover which workspaces and repos the signed-in user can access

​
Tips

  • Access is limited to what the connected Bitbucket user can see — not a shared service account unless that account connects.
  • List tools paginate with a page size capped at 100 (default is smaller).
  • Creating PRs and issues needs sufficient Bitbucket write permissions on the repo.
  • Prefer an explicit workspace and repo slug when names collide.
  • For GitHub or GitLab, use those toolkits instead (GitHub, GitLab).

​
Troubleshooting