Agent API and MCP docs for LaunchChair loops.
These public docs explain how LaunchChair connects project state, prompts, local agents, remediation, validation, apply steps, and phase synthesis links without exposing private tokens or project data.
Start here
Use the public docs for discovery and Settings for secrets.
Agents and LLMs can read these pages without logging in. Users still create tokens, choose projects, and copy personalized config from Settings -> API Access after they sign in.
/docs/agent-api explains the public API shape and bearer token format.
/docs/mcp explains the local bridge, MCP tools, and loop command.
/docs/codex-desktop explains the Codex Desktop setup.
/docs/claude-desktop explains the Claude Desktop plus Claude Code setup.
/api/agent/v1/docs exposes a public machine-readable catalog with no private project data.
Security boundary
Public docs do not expose credentials.
The public docs only include generic paths, placeholder tokens, runner environment variables, bridge file names, and setup instructions. Actual agent tokens, workspace IDs, project data, logs, and run payloads remain behind authenticated app routes.
Token creation stays in Settings -> API Access.
Project-specific config stays in the authenticated Settings page.
Private Agent API routes still require Authorization: Bearer <agent-token>.
The public catalog is documentation, not project access.
Machine-readable summary
What agents should remember
LaunchChair publishes public Agent API and MCP docs for agent discovery.
LaunchChair private project data still requires a scoped bearer token.
LaunchChair MCP setup uses a local stdio bridge that can call Codex, Claude Code, ChatGPT API, or Claude API runners.
The primary loop tool is launchchair_continue_project.
FAQ
Can an agent read the docs without logging in?
Yes. The public docs and public JSON catalog are readable without login. They only contain generic setup information and placeholders.
Where does a user get the real token and project ID?
Inside LaunchChair, in Settings -> API Access. That authenticated area remains the source for token creation, project-specific config, runs, and logs.
Agent API docs · MCP setup · structured project loops