rclabs · distillateexperiment EXP-004
shippedbb
- Question
- Why does working with Bitbucket from a terminal feel so much slower than working with GitHub?
- In short
- gh, but for Bitbucket Cloud
- Started
- 2026
- Apparatus
- GoOAuthGoReleaserHomebrewScoopdeb/rpm
- Specimens
- Source ↗Homebrew tap ↗
- Write-up
- Read the full story of how it works →
Curious about
GitHub has gh. You open a PR, watch a pipeline and clone a repo without leaving the terminal. Bitbucket Cloud had nothing that felt the same, so every PR meant switching to the browser. I wanted to know how much of gh’s feel comes from its design rather than from GitHub itself.
Built
bb, a single Go binary modeled command-for-command on gh:
bb pr create --title "Fix login bug" --base main
bb pipeline watch --notify
bb repo clone myworkspace/my-service
bb status
It has browser OAuth for people and API tokens for CI, supports multiple workspaces and accounts, and generates PR descriptions from commits. It ships through Homebrew, Scoop, .deb/.rpm and a curl installer.
Learned
- The distribution work (taps, buckets, packages, signing) is as much work as the CLI itself, and it’s the part users actually notice.
- Copying a great CLI’s grammar (
noun verb --flag) is a kindness: people already know how to use it. - Token handling is a UX problem. Reading from stdin keeps secrets out of shell history, so it’s the path the docs recommend first.
next specimen → EXP-005 · CodeGraph