a tech lead
An answer from a repo you never cloned.
whyThe question sits in code you have not opened in a year.
asksWhere does the billing repo retry failed invoices?
instibrain / works with / bitbucket
Bitbucket, worked with your own token.
The REST API and git over HTTPS, as you. Your token waits in your secret store until a call needs it.
team/tools/bitbucket/bitbucket.md slugs and review rulesasked · an exampleOpen the pull request for the invoice fix, with the usual reviewers.
the AI, from the pageOpened #412 into
main in billing, with your page's two reviewers in the same call.who uses it, and why
Who asks Bitbucket, and what for.
Answers from code, and changes to it, without a clone.
an engineering manager
The week's merges, for the update.
whyThe weekly update needs what actually merged.
asksList what merged into main in billing this week.
the CTO
A new repository, in the right project.
whyA new service needs a home, private from day one.
asksCreate a private repo for the invoice worker in Billing.
what you can ask
Your AI reads, searches and changes your repositories, mostly without a clone.
The API answers most questions alone. Git joins when the work needs the whole repository.
List and read repositories
The workspace's repositories, their details, their projects.
Create a repository or a project
Private by default. Needs the admin scope.
Open a pull request, reviewers included
Reviewers go in the same call, so notifications go out.
Read a file without cloning
A file, a directory, recent commits, merged pull requests.
Search the code
Each hit carries its path and matching lines.
Pull and push over git
Through a one-shot credential helper. No store keeps a copy.
where the credential stays
Your own token, your own scopes.
API tokens replace retired app passwords. A workspace admin grants your repositories.
in your Atlassian account, and in your secret store
Made in your Atlassian settings, kept in your secret store, read at use. The API takes your email with the token. Git takes your Bitbucket username.
in your brain
A page names the workspace, its repositories and its review rules.
what instibrain never touches
The token never sits in plain sight.
The token acts as you. Our server stores only the workspace page.
- The token in a URL or a config.
Read inside each call; for git, a one-shot helper keeps it off the process list.
- A repository you were not given.
A workspace admin decides what your account reaches.
- A pull request without its reviewers.
Required reviewers go into the creating call.
the limits
Your AI searches and creates within Bitbucket Cloud's own limits.
Three limits of the service itself.
| Limit | What it means |
|---|---|
| Code search is tokenised | An identifier misses longer identifiers that start with it. |
| Creating a repository needs admin | Without that scope, a token reads but cannot create. |
| App passwords are gone | An Atlassian API token is the one credential. |
before you connect it
Your AI pushes your code with your token, and we hold neither.
Does instibrain hold my Bitbucket token or my code?
No. The token stays in your secret store; code stays on Bitbucket and your computer.
What can the AI reach?
Your account's repositories, within your token's scopes.
Does it push?
Over git, when you ask, with your page's reviewers on the pull request.
Every pull request with the right reviewers.
Name the workspace and who reviews what. Claude Code and Codex then open pull requests your way, as you.