Sections written: - Getting Started (what-is-openacp, for-users, for-developers, for-contributors) - Platform Setup (Telegram, Discord, Slack) - Using OpenACP (commands, sessions, agents, permissions, voice, files) - Self-Hosting (installation, configuration, daemon, security, logging, updating) - Features (tunnel, context-resume, usage, persistence, handoff, doctor, assistant) - Extending (plugin-system, building-adapters, adapter-reference, contributing) - API Reference (CLI commands, REST API, config schema, env vars) - Troubleshooting (Telegram, Discord, Slack, agent issues, FAQ) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
961 B
961 B
Troubleshooting
Having trouble? Find solutions to common issues below.
Start here: run openacp doctor
The built-in diagnostic command checks your configuration, bot tokens, agent commands, and platform connectivity automatically. It catches the majority of setup issues in seconds:
openacp doctor
Each check reports a pass, warning, or failure with a specific message — fix the reported issues first before diving into the guides below.
Guides by topic
- Telegram issues — bot not responding, missing rights, topics, rate limits
- Discord issues — slash commands, intents, thread creation, interactions
- Slack issues — Socket Mode, token types, interactivity, channel creation
- Agent issues — command not found, crashes, timeouts, dependency errors
- FAQ — supported platforms, multiple users, costs, privacy, offline support