IDC puts 84% of developer time on work outside writing code: keeping READMEs current, cleaning up feature flags, generating release notes, triaging security findings. Atlassian’s answer is Bitbucket Agentic Pipelines, now in open beta.
An agent block in the pipeline file
You declare an agent next to your existing jobs in bitbucket-pipelines.yml, give it a prompt and scope constraints, then tie it to an event or schedule:
pipelines: pull-requests: '**': - agent: name: docs-sync prompt: 'Update the README and CHANGELOG to match this diff.' scope: ['README.md', 'CHANGELOG.md'] on: mergedOn a merged PR, the agent reads the diff, updates the relevant docs, and opens a pull request back to your branch. It carries read-only access, and every change runs through your normal review. You merge, or you do not.
Six chores ship today
The beta covers keeping READMEs in sync, fixing security vulnerabilities, cleaning up feature flags, generating release notes, summarizing large PRs, and finding test-coverage gaps. The last one matters for test teams: point the coverage-gap agent at your CI reports, and it raises a PR with extra tests against the low-coverage modules. A Playwright suite with thin coverage on a checkout module gets a drafted spec to review rather than a backlog ticket.
Automate the chores that matter but never make the sprint. Engineers review everything; the agent owns the first draft.
The setup cost
You need a paid Bitbucket Cloud plan and a Rovo Dev license, and the current agent runs Atlassian’s Rovo Dev model. Claude Code CLI support sits on the roadmap. This is the same direction GitHub took with agentic workflows, and the broader pattern is consistent: scope the agent narrowly, gate it behind review, and let it clear the work that quietly drains a sprint.
The scope is deliberate. The agent does not decide what ships. It hands you a first draft of the work you keep postponing, and you decide what is worth merging.
