Source control
The same repository and branch attribution, across every Bitbucket workspace.
Lineman attributes AI coding spend to the Bitbucket repository and branch it came from, across every workspace your account can see. Access is read-only: it lists workspaces, repositories and branch names, and never pushes code, comments on pull requests or writes to a repository. This covers Bitbucket Cloud, not Bitbucket Data Center.
Cost Explorer breaks AI spend down by repository and by branch. Lineman reads branch names, so a branch such as feat/LIN-412-retry-backoff links that session's cost to the work it belongs to, with nothing to add inside Bitbucket.
Tick the repositories your team is expected to work in. Nothing is ticked to begin with, and spend on anything unticked is flagged, so AI usage somewhere nobody was meant to be working stands out instead of blending into the total.
Repositories are discovered across all the workspaces your Bitbucket account can reach. Re-discovering only adds newly-found repositories and updates their details, so a repository you deliberately left unticked stays that way.
The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.
Read the setup guideEvery integration in one place, searchable by name and filterable by what it does.
View all integrations