Install
Install the CLI globally, then start login. Bonnie opens a browser so you can sign in with GitHub and create a CLI token.
npm install -g @bonniebuilds/codes bonnie login
bonnie login --token bon_<your-token>.Connect GitHub
Connect GitHub so Bonnie knows which repos you trust it with. From a repository you own or have access to:
cd /path/to/your/project bonnie repo connect
This installs or verifies the Bonnie Codes GitHub App for that repo and saves the Bonnie repo id locally.
Index memory
This is the turn: your repo becomes working memory. Bonnie agents can search it before answering questions or changing files.
bonnie index
Source map
Graphify captures code structure and relationships.
Architecture notes
MemPalace stores higher-level project memory.
Evidence lookup
Bonnie agents can query the indexed repository later.
Use agents where you work
Bring the memory back into the tool you already use, then choose the Bonnie workflow that matches the job.
bonnie setup bonnie agent bonnie mcp
Design
Turn rough requirements into a reviewed design and implementation plan.
Plan
Research architecture and map a safe path before coding.
Build
Make scoped code changes and run relevant checks.
Debug
Investigate failures with project memory and verified root cause.
Audit
Compare implementation against plans, docs, and evidence.
Scout
Gather focused, cited codebase evidence quickly.
Certified hosts
Host claims are generated from current certification evidence. A missing, failed, blocked, or expired matrix cell does not appear as support.
Bonnie agent
Full Bonnie agent via ACP
CLI reference
All Bonnie Codes commands. Run bonnie --help for the full help text with flags.
Authentication
| Command | Description |
|---|---|
| bonnie login | Sign in to Bonnie Codes with your GitHub account. Opens a browser to create a CLI token. |
| bonnie login --token bon_... | Save a pre-generated CLI token non-interactively. Use when you do not have a browser available. |
| bonnie logout | Revoke your token server-side and delete it locally. |
| bonnie account status | Show your account status, current plan, connected repos, and GitHub connection details. |
| bonnie account status --json | Print account status as JSON for programmatic use. |
Project setup
| Command | Description |
|---|---|
| bonnie | Bare command. Bootstraps the repo if needed and starts an interactive ACP session. |
| bonnie init | Explicitly bootstrap the current repo. Creates a .bonnie/ directory with the native manifest and built-in agents. |
Repository management
| Command | Description |
|---|---|
| bonnie repo connect | Connect the current GitHub repository. Opens the Bonnie Codes GitHub App install flow, then saves the repo id locally. |
| bonnie github connect | Alias for bonnie repo connect. |
| bonnie repo activate | Activate a connected repository by providing the GitHub repo id, owner, and name. |
Memory & indexing
| Command | Description |
|---|---|
| bonnie index | Start a repository index job and observe its durable completion state. |
| bonnie memory configure | Save the memory API endpoint and mode (cloud, self_hosted, local) to your global config. |
| bonnie memory start-local | Start a self-hosted memory server on your local machine. Default port is 7391. |
| bonnie memory stop-local | Stop the running local memory server. |
Integration
| Command | Description |
|---|---|
| bonnie setup | List available client adapters and configure the current repo for Bonnie Codes. |
| bonnie acp | Start a JSON-RPC 2.0 ACP provider over stdio. Used by ACP-compatible clients. ACP owns the full Bonnie session and subagent protocol. |
| bonnie mcp | Start a JSON-RPC 2.0 MCP server over stdio. Exposes Bonnie tools (file, shell, memory) for MCP-compatible clients. |
Ready?
Start with the CLI and one real repo.