# Platform Adapters

> Overview of all platform adapters available for connecting to Archon.

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

| Adapter | Transport | Auth Required | Setup |
|---------|-----------|---------------|-------|
| [**Web UI**](/adapters/web/) | SSE streaming | None | Built-in |
| [**CLI**](/reference/cli/) | stdout | None | Built-in |
| [**Slack**](/adapters/slack/) | Socket Mode | Bot + App tokens | [Setup guide](/adapters/slack/) |
| [**Telegram**](/adapters/telegram/) | Bot API polling | Bot token | [Setup guide](/adapters/telegram/) |
| [**GitHub**](/adapters/github/) | Webhooks | Token + webhook secret | [Setup guide](/adapters/github/) |

## Community Adapters

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

| Adapter | Transport | Auth Required | Setup |
|---------|-----------|---------------|-------|
| [**Discord**](/adapters/community/discord/) | WebSocket | Bot token | [Setup guide](/adapters/community/discord/) |
| [**Gitea**](/adapters/community/gitea/) | Webhooks | Token + webhook secret | [Setup guide](/adapters/community/gitea/) |
| [**GitLab**](/adapters/community/gitlab/) | Webhooks | Token + webhook secret | [Setup guide](/adapters/community/gitlab/) |

## 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

- **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.