Operator and architecture docs for acpbot — Telegram as a control surface for ACP coding agents.
Current release: v0.4.0 — download binaries · install guide
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, Docker) - 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 skills (telegram, schedules, multi-agent, autoreview, eve) |
| OAuth | Remote MCP auth (PKCE + DCR) |
| Multi-agent | Spawn child agents via MCP; worktrees + A2A |
| Review | Dual-agent closeout review (/review, review_run) |
| EVE | Agent-authored directive graphs; host orchestration; leaf schema handoff |
| Multi-host | Run acp-host on other machines; route repos over WSS |
| Commands | Plan exit approve, message reactions → agent, queue/steer |
| Agents | Permissions vs plan mode; plan-exit always asks |
Source
High-level overview and install: GitHub README · Releases