Prerequisites
- A Bitbucket Cloud account with access to the workspace you want CloudThinker to reach.
- Your workspace slug — the segment after
bitbucket.org/in your repository URLs. - For access tokens: permission to create a workspace, project, or repository access token. Workspace and project tokens require a Bitbucket Premium plan; repository tokens are available on the free plan.
Setup
Navigate to Connections → Bitbucket in your CloudThinker workspace, click Connect, then pick an authentication method.- OAuth
- Access token
1
Enter your workspace slug
Type the Bitbucket Workspace slug (e.g.
my-workspace). The OAuth flow cannot start without it.2
Authorize CloudThinker
Click Connect to Bitbucket, sign in to the Bitbucket account with access to that workspace, and approve access.
3
Return to CloudThinker
After authorization, CloudThinker stores the OAuth tokens and shows a Connected status.
Bitbucket webhooks for Review are registered automatically — no manual webhook configuration is needed.
Connection details
Required permissions
- OAuth inherits the workspace access of the authorizing Bitbucket account.
- Access tokens need Account Read, Repositories Read/Write, Pull requests Read/Write, Webhooks Read and write, and Pipelines Read/Write.
- Write operations such as branch and pull request changes additionally require explicit approval in CloudThinker.
Repository access
On top of what your OAuth account or access token can reach, the connection carries a CloudThinker-side repository policy. Open the connection’s detail panel and find Repository access under Settings:
The policy only ever narrows what the credential already grants, and it is separate from choosing which repositories run Review. Switching from Selected to All and back restores your previous selection.
Agent capabilities
Once connected, agents can:Verify the connection
Example prompts
Write access
Reads run without approval. Any change to a branch or a pull request is approval-gated: CloudThinker states the effect and the exact inputs, then waits for your confirmation before touching the repository.Troubleshooting
Token validation fails
Token validation fails
The token is expired, lacks one of the required permissions, or the token type does not match your plan — workspace and project tokens need Bitbucket Premium. Create a new token with the permissions listed above and validate again.
Connected, but CloudThinker asks for a workspace slug
Connected, but CloudThinker asks for a workspace slug
An OAuth connection without a stored workspace slug cannot resolve your repositories. Enter the slug in the recovery form CloudThinker shows on the connection to finish setup.
Agent cannot find an expected repository
Agent cannot find an expected repository
A repository token reaches one repository, and a project token only that project’s repositories. Reconnect with a broader token, or with an account that has access to the missing repository.
Security
- Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
- Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
- Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
- Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
- Scoped tokens — a repository or project access token limits CloudThinker to exactly the code it should reach.
- Set expirations — give tokens an expiration date and rotate them before they lapse.
Related
Review Setup
Turn on automated AI code reviews for your Bitbucket repositories
Provider Authentication
Authentication details for every Review provider