bb — the ZeroShot CLI
Once installed, everything ZeroShot does on your machine runs through a single binary: bb. It’s small, scriptable, and stays out of your way until you call it.
Day-to-day commands
These are the commands you’ll actually type. The rest are below.Sessions
The CLI tracks every session you have with a supported coding agent (Claude Code, Codex, Cursor, etc.) and indexes it by repo · branch · commit · author. See the Agent Sessions page for the full story; here’s the command surface.Skills
Skills are slash commands like/bb-specify and /trust-but-verify that get installed into your coding agent. They’re shipped as packs — see the Skills reference for what each one does.
Account & sync
bb login is optional. Without it, sessions stay on disk and only resume on the same machine.
Diagnostics & maintenance
bb doctor is the first thing to run when something feels off. Sample output:
Repo configuration
bb stores per-repo settings in .buildbetter/ at the repo root (it’s safe to commit). Use these to opt repos into different defaults — for example, a repo where sessions should never sync to the cloud.
Where things live
Scripting bb
Most commands support --json for machine-readable output, which makes bb easy to wire into pre-commit hooks, PR templates, or CI:
0 success, 1 user error, 2 not signed in, 3 network failure, 4 integrity / corrupted state.
Next steps
Sessions deep dive
What’s in a session, where it’s stored, how resume actually works
Skills
The slash commands that ship in each pack