Skip to main content

​
Limitations

CapabilityStatusNotes
Free/Standard tiersNot supportedworkspace access tokens are only supported in Premium plan.
Choose individual repos to indexNot supportedQodo Context Engine will index all repositories the token can see. If you need to limit scope, create a token tied to a workspace / user that has access only to the desired repos.
Webhooks / Marketplace appN/ABitbucket Cloud integration is token-only – no webhooks or Atlassian Connect app is required.

​
1. Generate an Access Token

Qodo Context Engine accepts either a Workspace Access Token or a Personal App Password. Both must have read-only scopes. Prerequisite – you must be a Workspace Administrator.
1

In Bitbucket, open Workspace settings ▸ Access management ▸ Access tokens.

2

Click Create access token.

  • Name – something like “context-engine”.
  • Permissions – tick Repositories: Read, Projects: Read, Pull requests: Read.
3

Click Create and copy the raw token immediately – Bitbucket shows it only once.

​
Personal App Password (Alternative)

1

Click your avatar ▸ Personal settings ▸ App passwords.

2

Click Create app password and give it a meaningful label.

3

Enable the same read-only scopes listed above, and add Workspace: Read permission

(read:workspace:bitbucket).
4

Generate and copy the password (it will not be shown again).

​
2. Send relevant information to Qodo

[bitbucket_cloud]
[bitbucket_cloud.tokens]
# Option A – workspace token
"my-workspace-name" = "XXXXXXXXXXXXXXXXXXXXXXXX"

# Option B – personal app-password
"user@example.com" = "YYYYYYYYYYYYYYYYYYYYYY"

​
Key

Token typeKey (left-hand-side)Value (right-hand-side)
Workspace token”<WORKSPACE_SLUG>""<WORKSPACE_ACCESS_TOKEN>“
App password”<USER_EMAIL>""<APP_PASSWORD>”