Bitbucket Data Center: clone, push and open PRs with one token

A self-hosted Bitbucket (Data Center / Server, bitbucket.yourcompany.com) has no login an application can run on its own without its administrator, so this one takes a single paste: click Connect Bitbucket in Settings → Git accounts, type the host, follow the link to its HTTP access tokens page (your profile → Manage account → HTTP access tokens), create a token with Project → Read and Repository → Write, paste it, Connect. Sessionboxer checks the token against the host, finds out whose it is and shows Connected as @you on bitbucket.yourcompany.com; the token is stored like any other secret header and never shown or snapshotted. Add one entry per host or account.

Unlike GitHub's, this entry adds no MCP server: it is a login for the box. While it is enabled for a session, git clone/git push to that host and bb — a gh-like CLI for Bitbucket Data Center that ships in the Sandbox image — work as that account: bb pr create, bb pr list, bb pr view --comments, bb pr checks, bb pr comment [--reply-to], bb pr approve / request-changes and bb api <path>. Git asks bb auth git-credential, whose hosts.yml the Daemon writes on tmpfs exactly like gh's, so switching the entry off removes the login and Snapshots never carry it. Merging a PR is not among the commands (Bitbucket does not let HTTP access tokens merge; bb pr view --web opens it in the browser). The PRs pane follows Bitbucket pull requests with this entry's token — see Pull requests attached to a session. Bitbucket Cloud (bitbucket.org) is not covered.