Bonnie Codes · setup

Teach Bonnie your repo.

Install the CLI, connect GitHub, index memory, and run the engineering loop from your editor or terminal.

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
No browser on that machine? Open CLI login somewhere else, create a token, then run 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

CommandDescription
bonnie loginSign 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 logoutRevoke your token server-side and delete it locally.
bonnie account statusShow your account status, current plan, connected repos, and GitHub connection details.
bonnie account status --jsonPrint account status as JSON for programmatic use.

Project setup

CommandDescription
bonnieBare command. Bootstraps the repo if needed and starts an interactive ACP session.
bonnie initExplicitly bootstrap the current repo. Creates a .bonnie/ directory with the native manifest and built-in agents.

Repository management

CommandDescription
bonnie repo connectConnect the current GitHub repository. Opens the Bonnie Codes GitHub App install flow, then saves the repo id locally.
bonnie github connectAlias for bonnie repo connect.
bonnie repo activateActivate a connected repository by providing the GitHub repo id, owner, and name.

Memory & indexing

CommandDescription
bonnie indexStart a repository index job and observe its durable completion state.
bonnie memory configureSave the memory API endpoint and mode (cloud, self_hosted, local) to your global config.
bonnie memory start-localStart a self-hosted memory server on your local machine. Default port is 7391.
bonnie memory stop-localStop the running local memory server.

Integration

CommandDescription
bonnie setupList available client adapters and configure the current repo for Bonnie Codes.
bonnie acpStart a JSON-RPC 2.0 ACP provider over stdio. Used by ACP-compatible clients. ACP owns the full Bonnie session and subagent protocol.
bonnie mcpStart 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.

Start setup