> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ageneral.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Channels

> Inbound messaging surfaces for an agent

## Overview

**Channels** are **inbound** surfaces the agent listens on—for example **Telegram**, **Discord**, or browser-based control experiences. Traffic is handled by the **OpenClaw gateway**, which applies **channel** configuration.

## Configuration

Each channel has settings for tokens, **pairing**, direct-message policy, and related options. Ageneral merges **project** defaults with **agent** overrides before updating the gateway.

## Connectors vs channels

**Connectors** supply OAuth and MCP integrations from the catalog. See [Connectors](/guides/agents/connectors). Choosing a **connector** is separate from choosing which **channels** the gateway listens on.

## Pairing

Many channels require explicit **pairing** before new chats or groups are trusted. Complete the steps shown in the product when pairing is required.

## Troubleshooting

If inbound traffic stops:

1. Confirm the **channel** is enabled.
2. Confirm required **connectors** are enabled.
3. Allow time for the latest configuration to apply.

## Next steps

* [Connectors](/guides/agents/connectors)
* [OpenClaw runtime](/guides/agents/openclaw)
* [Agents](/agents)