Skip to content

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.

AdapterTransportAuth RequiredSetup
Web UISSE streamingNoneBuilt-in
CLIstdoutNoneBuilt-in
SlackSocket Mode, as a chat pluginPlugin + Bot and App tokensSetup guide
Telegram (deprecated)Bot API pollingBot tokenSetup guide
GitHubWebhooksToken + webhook secretSetup guide

Community adapters follow the same IPlatformAdapter interface but target platforms outside the core set.

AdapterTransportAuth RequiredSetup
DiscordWebSocketBot tokenSetup guide
GiteaWebhooksToken + webhook secretSetup guide
GitLabWebhooksToken + webhook secretSetup guide

Slack runs as a chat plugin: a separate process the server starts from an installed plugin, speaking the chat plugin protocol. The other adapters are built into the server. All bundled 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
  • Web UI is the fastest way to get started — no tokens or external services needed.
  • Slack is 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 bundled adapter with the required environment variables set will start automatically when you launch the server. Slack also needs its plugin installed; see the Slack guide.