Chat integrations

Chat integrations let the team ask an agent questions, @-mention it in a channel, or create issues from Slack without opening Kolleague.

Slack connections can be created and managed from workspace settings. Each Slack app installation is bound to one Kolleague agent. To use several agents, connect a separate Slack app for each.

See Slack Bot integration for setup instructions.

How a message is processed

1. Slack delivers a direct message, app mention, or slash command.
2. Kolleague resolves the installation, Slack identity, workspace, and agent.
3. The message is attached to the matching Kolleague chat session.
4. The agent runs through its configured runtime.
5. Kolleague posts the response back to Slack.

Ordinary messages follow this flow. /issue is a command, not a chat turn: Kolleague posts the result back to the originating platform but does not add the command to Kolleague Chat. Slack's native slash command continues through its separate asynchronous issue-creation flow.

Session isolation

Slack separates direct messages by channel. In a channel, each thread holds its own session.

Follow-ups in a channel still need a fresh @-mention. The agent receives only messages addressed to it; it does not read the whole channel automatically.

Link member identities

The first time someone messages an agent, the bot may ask them to link their Slack identity to their Kolleague account. The link is short-lived and must be opened while signed in.

Identity links are scoped to the installation and workspace. They are not shared with another workspace or Slack app.

Manage connections

Workspace owners and admins can connect or disconnect Slack apps. Regular members can view connected integrations and use agents they can access.

After disconnecting, the bot stops receiving new messages. Existing Kolleague conversations and run records are kept.

Next steps

• Slack Bot integration — connect an agent to Slack.
• Chat — understand the conversation and execution model behind the bot.