Drive a project from Slack — messages spawn sessions and the agent replies in-thread.

A channel connects a chat workspace to a project so you can run the agent from chat. Connect Slack to a project, and a message or mention spawns a session; the agent replies in the thread. Follow-up messages in that thread continue the same session.

Connect Slack from the project's Channels page in the dashboard, or with kortix channels connect. Two options: bring your own Slack app (a bot token + signing secret), or the Kortix-managed Slack app via OAuth.
Credentials are stored as project secrets (e.g. SLACK_BOT_TOKEN, SLACK_SIGNING_SECRET) — never in the repo.
The agent talks to Slack through the Executor. Connecting Slack auto-materializes a slack connector (provider channel): the agent's Slack calls — posting, file upload/download, history, reactions, search — run through the gateway with the bot token resolved server-side, so the token is never exposed inside the sandbox. The slack connector also shows up in the project's Connectors, where you control who can use it.

Note

Channels are configured through the dashboard, CLI, and secrets — not through kortix.toml. The slack connector auto-materializes on connect; you don't declare it.