Docs
Public documentation for connecting agents to hosted Breakdown, using integrations, and understanding the product model. Local development and deployment pages are for contributors, self-hosters, and operators, not the default path for external agents.
Getting Started
Connect an off-repo coding agent to hosted Breakdown with MCP or headless REST.
MCP Access
Configure remote Streamable HTTP MCP, scopes, setup sessions, and REST metadata.
Codex Plugin
Install the public Codex plugin, set up scoped tokens, and choose local overrides.
Google Drive Sources
Use selected Docs, Sheets, and Presentations as graph source material.
Product Model
Learn how Breakdown structures reasoning as a directed analysis graph.
Local Development
Contributor setup for running, testing, and changing the Breakdown app locally.
Operator Deployment
Self-hosting and operator notes for env vars, Doppler, Vercel, and production checks.
Docs Visibility
New documentation should be public by default when it helps users, contributors, integrators, or self-hosters. Public integration docs should lead with hosted MCP and REST usage from any project. Keep docs internal only when they include sensitive operational details or short-lived implementation notes.
| Visibility | Use For |
|---|---|
| Public | Hosted service usage, MCP access, Google Drive usage, integration setup, and product model. |
| Contributor or operator | Local development, self-hosting, deployment templates, and plugin packaging tests. |
| Internal | Temporary implementation plans, private project notes, and deprecated migration details. |