The CLI ships in the same binary as the server. Most users install the full build alongside the server itself, then useDocumentation Index
Fetch the complete documentation index at: https://docs.breadbox.sh/llms.txt
Use this file to discover all available pages before exploring further.
breadbox auth login to drive other Breadboxes from the same machine. Agent and ops hosts that should never run a server install the lite build (breadbox-cli) instead.
Pick a build
- Full (server + CLI + dashboard)
- Headless (server + CLI, no dashboard)
- Lite (CLI only)
Default build. One binary that runs
breadbox serve (full HTTP server), breadbox mcp (stdio MCP host), and every CLI command. This is what the Quickstart installs.Use this when you want one machine that hosts Breadbox and can also drive a remote Breadbox via breadbox auth login.From a pre-built release
Download
Grab the binary for your platform from the GitHub releases page. Release artifacts include
breadbox (full) and breadbox-cli (lite) for linux-amd64, linux-arm64, darwin-amd64, darwin-arm64.From source
You need Go 1.24 or later.-ldflags "-X main.version=<tag>"; without that flag the binary reports dev.
Shell completion
The CLI ships completion scripts for bash, zsh, and fish.gh or kubectl.
Verify the install
serve, mcp, init, migrate, reveal-key, and backup. If a server-only command shows up under breadbox-cli --help, you’ve grabbed the full binary by accident.
Next steps
Authenticate
Add a host and mint a key with device-code login or paste mode.
Headless deployment
Drive a remote Breadbox from an agent host.