Operator and architecture docs for acpbot — Telegram as a control surface for ACP coding agents.
Start here
- Getting started — release binary, setup, pair, first topic
- Pairing — CLI operator approve flow
- Repos —
acpbot repomanager + folder browser - Configuration —
config.tomlreference (paths, speech, OAuth) - Commands — lobby vs topic slash surface
How it works
| Doc | Topic |
|---|---|
| Architecture | Worker, acp-host, sockets, store layout |
| Agents | Built-in agents, /model, /agent |
| MCP | Built-in acpbot tools, per-repo servers, profiles |
| Worker API | Unix HTTP API MCP → Telegram |
| Schedules | Durable delayed/recurring jobs + host ticker |
| Skills | Bundled telegram + schedules skills, global install |
| OAuth | Remote MCP auth (PKCE + DCR) |
Source
High-level overview and install: GitHub README.