Connect OpenClaw to Bitbucket

September 13, 2026Claworc Team

Tags:integrations

Bitbucket is Atlassian’s Git hosting service, and for teams already living in Jira and Confluence it is usually where the code lives too. Along with the repositories comes a steady stream of small chores: opening pull requests with a proper description, chasing reviewers, checking whether the last pipeline went green, and answering “which branch has that fix?” for the fourth time in a week.

With Claworc’s External Connections, an OpenClaw agent can do that work inside your Bitbucket workspace on your behalf. You sign in to Bitbucket once through a popup, Composio holds the resulting OAuth token, and the agent gets an auto-generated claworc-bitbucket skill that tells it which Bitbucket tools exist and how to call them. The agent never sees a password, an OAuth token or an app password.

Tools available to OpenClaw agents

Composio’s Bitbucket toolkit exposes 105 actions covering repositories, pull requests, issues, commits, pipelines and webhooks. In practice an OpenClaw agent leans on a handful of capabilities:

• Open pull requests — create a PR from one branch to another with the title, description and reviewers already filled in.
• Review open PRs — see what is open, who is assigned, and read the full context of a single PR.
• Comment on a PR — leave review feedback or a status note directly on the PR.
• Approve and merge — sign off and merge once the checks have passed.
• Manage branches — start work on a fresh branch or find out what already exists.
• Browse commits — walk the history of a branch and inspect one commit in detail.
• Track issues — file and review issues where a repo uses Bitbucket’s built-in tracker.

Every tool is called through a small broker running next to the agent, so the agent only needs to describe what it wants done in plain language and let the skill handle the rest.

Use cases

Open a pull request from a finished change

Once the agent has pushed a fix to a branch, ask it to “open a PR against main, summarize the change from the commits, and add the two people who own this module as reviewers.” It builds the description from the branch’s commits and opens the PR, so it arrives with context instead of an empty body.

Daily review queue

Each morning, have the agent list the open pull requests across your workspace, filter to the PRs waiting on your team, and post a short list: what each one changes, how long it has been open, and whether it is blocked on a reviewer. Anything stale for more than two days gets a polite nudge as a comment on the PR.

Answer “where is that change?”

“Did the retry fix land in release/2.4?” The agent walks the commit history of that branch, matches the commit message, and replies with the hash and date. No more checking out branches locally just to answer a question in chat.

Get started

Connecting Bitbucket takes three steps: an admin adds a Composio API key to Claworc’s settings, you open the instance’s Settings tab, click + Add connection, pick Bitbucket and sign in to Atlassian. The claworc-bitbucket skill appears in the instance a moment later. The full walkthrough, including the exact Composio permissions the key needs, is in the External Connections documentation.