Sanaf AI
Start free
Developer Tools

Bitbucket, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Bitbucket account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Signs in to your account
  • 17 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Bitbucket is

Bitbucket is a Git-based code hosting and collaboration platform supporting private and public repositories, enabling teams to manage and review code through pull requests and integrations

You sign in with your own Bitbucket account, the same way you already do. We never see or hold your password.

How a run works

One message in, the work done in Bitbucket.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Bitbucket. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Bitbucket account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

17 tools it already has

What it can do in Bitbucket

These are the ready-made tools your AI employee already has in Bitbucket. It is not limited to them, but it never has to be taught these.

  • Create a branchCreates a new branch in a bitbucket repository from a target commit hash; the branch name must be unique, adhere to bitbucket's naming conventions, and not include the 'refs/heads/
  • Create a pull requestCreates a new pull request in a specified bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
  • Create an issueCreates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, v
  • Create an issue commentAdds a new comment with markdown support to an existing bitbucket issue.
  • Create repositoryCreates a new bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if project key is not provided.
  • Create snippet commentPosts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
  • Delete issuePermanently deletes a specific issue, identified by its issue id, from the repository specified by repo slug within the given workspace.
  • Delete repositoryPermanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.
  • Get current userRetrieves the profile information (uuid, display name, links, creation date) for the currently authenticated bitbucket user.
  • Get file from repositoryRetrieves a specific file's content from a bitbucket repository at a given commit (hash, branch, or tag), failing if the file path is invalid for that commit.
  • Get Pull RequestGet a single pull request by id with complete details.
  • Get snippetRetrieves a specific bitbucket snippet by its encoded id from an existing workspace, returning its metadata and file structure.
  • List pull requestsLists pull requests in a specified, accessible bitbucket repository, optionally filtering by state (open, merged, declined).
  • List repositories in workspaceLists repositories in a specified bitbucket workspace, accessible to the authenticated user, with options to filter by role or query string, and sort results.
  • List workspace membersLists all members of a specified bitbucket workspace; the workspace must exist.
  • List workspacesLists bitbucket workspaces accessible to the authenticated user, optionally filtered and sorted.
  • Update an issueUpdates an existing issue in a bitbucket repository by modifying specified attributes; requires workspace, repo slug, issue id, and at least one attribute to update.
Access, and who is in charge of it

You stay the boss of your Bitbucket account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Bitbucket account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Bitbucket is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Bitbucket and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Bitbucket

Can an AI employee really work inside Bitbucket?
Yes. It signs in to your own Bitbucket account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Bitbucket?
No. Nothing moves and nothing is replaced. Your records stay in Bitbucket, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Bitbucket account?
You sign in with your own Bitbucket account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Bitbucket?
It has 17 ready-made tools in Bitbucket today, among them Create a branch, Create a pull request and Create an issue. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Bitbucket and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Bitbucket and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Bitbucket?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Bitbucket is written down with what it did and when.