Platform Adapters
Archon supports multiple platform adapters. Each adapter connects Archon to a different communication channel, letting you trigger workflows and interact with AI agents from wherever you work.
Core Adapters
Section titled “Core Adapters”| Adapter | Transport | Auth Required | Setup |
|---|---|---|---|
| Web UI | SSE streaming | None | Built-in |
| CLI | stdout | None | Built-in |
| Slack | Socket Mode | Bot + App tokens | Setup guide |
| Telegram | Bot API polling | Bot token | Setup guide |
| GitHub | Webhooks | Token + webhook secret | Setup guide |
Community Adapters
Section titled “Community Adapters”Community adapters follow the same IPlatformAdapter interface but target platforms outside the core set.
| Adapter | Transport | Auth Required | Setup |
|---|---|---|---|
| Discord | WebSocket | Bot token | Setup guide |
| Gitea | Webhooks | Token + webhook secret | Setup guide |
| GitLab | Webhooks | Token + webhook secret | Setup guide |
How Adapters Work
Section titled “How Adapters Work”All adapters implement the IPlatformAdapter interface. They handle:
- Message ingestion — receiving messages from the platform and forwarding them to Archon’s orchestrator
- Response delivery — streaming or batching AI responses back to the platform
- Authorization — optional user whitelists to restrict access
- Conversation tracking — mapping platform-specific identifiers (thread IDs, chat IDs, issue numbers) to Archon conversations
Choosing an Adapter
Section titled “Choosing an Adapter”- Web UI is the fastest way to get started — no tokens or external services needed.
- Slack and Telegram are ideal for mobile access and team collaboration.
- GitHub integrates directly into your issue and PR workflow.
- Discord works well for community or team servers.
You can run multiple adapters simultaneously. Any adapter with the required environment variables set will start automatically when you launch the server.