Connect an adapter

Each platform has its own credentials and its own way of authenticating a bot, but every adapter ends at the same place: an *_AGENT_KEY naming which registered agent should answer.

Slack needs the most pieces:

SLACK_BOT_TOKEN=xoxb-...
SLACK_SIGNING_SECRET=...
SLACK_BOT_USER_ID=U...
SLACK_TEAM_ID=T...
SLACK_AGENT_KEY=assistant

Discord follows the same idea with fewer parts:

DISCORD_BOT_TOKEN=...
DISCORD_APPLICATION_ID=...
DISCORD_AGENT_KEY=assistant

Once you have seen two, the rest are predictable - platform credentials, then the agent key.

Two things to configure

Keep credentials in your deployment's secret store. These are bot tokens with real reach into a workspace, and they belong nowhere near the config repository.

Point the adapter at an agent designed for chat. An agent whose response format assumes a web page will produce enormous replies in Slack. See Control channel behavior for what to change.

Attachments coming in from a channel flow through AXL's normal attachment system after the adapter fetches them, subject to platform and server size limits.

Next

• Control channel behavior - reply modes and formatting for chat.
• Create your first agent - if you do not have an agent key yet.
• Channel adapter reference - every supported adapter and variable.