Gamut

Chat Integrations Overview

Connect your agents to messaging platforms so they can respond to messages in real-time.

Chat integrations let you connect a Superagent agent to an external messaging platform so it can receive and respond to messages directly inside the chat app. Instead of interacting with your agent only through the Superagent desktop UI, you (and others) can message it from Telegram, Slack, or iMessage.

Supported Platforms

  • Telegram — Connect a Telegram bot to your agent. Anyone who messages the bot gets a response from the agent.
  • Slack — Connect a Slack bot to your agent. The bot can respond to direct messages and channel conversations, with fine-grained control over when and how it replies.
  • iMessage — Connect your phone number to an agent through the iMessage gateway service. Send a text, get a response.

How It Works

When you set up a chat integration, Superagent creates a persistent connection between the messaging platform and your agent:

  1. A message arrives from the external platform (a Telegram DM, a Slack message, an iMessage text).
  2. Superagent routes the message to the configured agent. If no session exists for that conversation yet, a new agent session is created automatically.
  3. The agent processes the message using its configured tools, skills, and system prompt, just as it would for messages sent from the desktop UI.
  4. The response streams back to the chat platform. For Telegram and Slack, the response is streamed progressively (the message updates as the agent types). For iMessage, the full response is sent once complete.

The agent has access to all of its normal capabilities during a chat integration session: connected accounts, MCP servers, browser use, file handling, and multi-agent delegation all work as expected. A few actions that require the desktop UI (such as OAuth authorization flows or browser input) will prompt the user to open Superagent on their computer.

Sessions

Each unique conversation in the external chat creates a corresponding session in Superagent. For example:

  • Each Telegram user who DMs the bot gets their own session.
  • Each Slack user who DMs the bot, or each channel the bot is active in, gets a session.
  • An iMessage conversation gets a session.

Sessions are visible in the Superagent sidebar under the integration, and you can view the full message history in the desktop app. These sessions are read-only in the UI since messages can only be sent from the connected chat platform.

Session Timeout

You can optionally configure a session timeout (in hours). When the timeout elapses since the last message in a conversation, the next incoming message will start a fresh session instead of continuing the old one. This is useful for agents that should treat each interaction as independent after a period of inactivity.

If no timeout is set, the same session persists indefinitely for each conversation.

Clearing Sessions

You can manually clear a session at any time, either from the Superagent UI or by sending /clear in the chat. The next message will start a fresh session.

Common Settings

All chat integrations share these options:

  • Bot Name — A display name for the integration, shown in the Superagent sidebar.
  • Show Tool Calls — When enabled, the bot posts a message in the chat each time the agent invokes a tool, so the user can see what the agent is doing.
  • Session Timeout — Number of hours of inactivity after which the next message starts a new session. Leave blank to keep a single continuous session.
  • Model and Effort — Override the model or effort level used for this integration's sessions.

Next Steps