CONNECTOR · BITBUCKET
Ground every plan in your Bitbucket code.
A connector is the bridge to your code. Bitbucket Cloud and Bitbucket Data Center are two different products with two different APIs, so Plansmith connects to each on its own terms. Either way the planning agent gets read-only access to the repository you link, and it never changes a line.
What the agent reads
Link a repository and the agent reads your Bitbucket code while it interviews you, so every Spec fits the product as it works today. Read access only. It never changes a line.
| What Plansmith reads | What it grounds |
|---|---|
| Repository files and folders | Where things live, so a Spec names the real modules instead of a guess |
| File contents on the default branch | How the product works today, so the plan starts from what exists |
| Full-text search across the repository, cloud or self-hosted | The exact places a change lands, before anyone sizes it |
| Framework, styling, and component conventions | A prototype that looks like your product, not a generic mockup |
| The repository you link to a Project | Code context on every Plan in that Project |
| Nothing else | Read access only. The agent never writes, commits, branches, or opens a pull request. |
Three steps to grounded plans
- 1
Connect
For Bitbucket Cloud, click Connect Bitbucket and sign in with your Atlassian account. For Data Center, register your server's address first and connect to that. Connections are personal, and access is read only.
- 2
Link a repository
Pick the repository this Project plans against. The agent reads its default branch. One repository per Project, and you can change it whenever the work moves.
- 3
Plan
Describe what you need. The agent reads the code while it interviews you, so the Specs land on the product you already have. You never open the repo.
Questions, answered
- Can Plansmith change our code?
- No. The connector is read only. The agent lists files, reads them, and searches on the default branch, and that is the entire surface. It never writes, commits, branches, or opens a pull request.
- We use Data Center, not Cloud. Does that work?
- Yes, as its own connection. Cloud and Data Center are different products with different APIs, so Plansmith treats them as two connectors rather than one with a checkbox. Register your Data Center address once, connect, and link a repository the same way. The server has to be reachable over public HTTPS, and registering one is an owner's job.
- Can the agent search our code?
- Yes, cloud or self-hosted. The agent searches every file in the repository with the same tools your developers use, and it reads the code while it interviews you.
- Does Plansmith keep a copy of our code?
- Yes, a text copy of the branch you link, so the agent can search all of it. It refreshes when the branch moves and is deleted when you unlink the repository. Through the private-network connector, the copy is built inside your network and then uploaded.
- Do I need to connect a repository before I start planning?
- No. Plan first and add code context whenever you want it. A plan without it still produces build-ready specs and prototypes. A plan with it produces Specs that fit the product you already have.
Grounded in your repo, not your imagination.
Other code connectors: GitHub · GitLab · All connectors