Messaging

Spacebot connects to chat platforms so your agent can talk to people where they already are. You can connect multiple platforms at once — messages from all of them flow into the same agent system.

Supported Platforms

How It Works

1. You connect a platform by adding your tokens in the dashboard or config
2. Spacebot opens a persistent connection to that platform
3. When someone sends a message, Spacebot receives it and decides whether to reply, skip, or delegate work
4. Each conversation (channel, thread, DM) gets its own isolated history

You can connect multiple platforms at the same time. An agent on Discord and Slack simultaneously is just two bindings pointing at the same agent.

For Email specifically, Spacebot treats inbound mail as intake-first by default: triage, memory capture for meaningful non-spam messages, and escalation to other channels for urgent items. Inbound email channels do not auto-reply. When the Email adapter is configured, intentional outbound email can still be initiated from other channels using an explicit target such as email:[email protected].

Bindings

Bindings route messages from a platform to a specific agent. A binding says "messages from this place go to this agent."

# Route a Discord server to the main agent
[[bindings]]
agent_id = "main"
channel = "discord"
guild_id = "123456789"

# Route only the named Discord adapter instance `ops`
[[bindings]]
agent_id = "main"
channel = "discord"
adapter = "ops"
guild_id = "987654321"

# Route a Slack workspace to the main agent
[[bindings]]
agent_id = "main"
channel = "slack"
workspace_id = "T01234ABCDE"

# Route a Telegram chat to a different agent
[[bindings]]
agent_id = "support-bot"
channel = "telegram"
chat_id = "-100123456789"

Without any filtering (no guild ID, workspace ID, or chat ID), a binding accepts messages from anywhere on that platform.

Named adapters use adapter = "<name>" in bindings. Omit adapter to target the platform default adapter (discord, slack, telegram, twitch, email, webhook).

If no binding matches an incoming message, it's routed to the default agent automatically. This means the bot responds everywhere out of the box — add bindings to restrict it to specific channels or servers.

Multiple Agents

You can run multiple agents on the same Spacebot instance, each connected to different places. Each agent has its own memory, personality, and conversation history.

[[agents]]
id = "main"
default = true

[[agents]]
id = "support-bot"

# Main agent handles Discord
[[bindings]]
agent_id = "main"
channel = "discord"
guild_id = "123456789"

# Support bot handles Slack
[[bindings]]
agent_id = "support-bot"
channel = "slack"
workspace_id = "T01234ABCDE"

Conversations

Each chat context maps to its own Spacebot conversation with isolated history:

Threads are first-class on Discord and Slack — a thread gets its own conversation, separate from the parent channel.

Streaming

Responses stream in real-time on platforms that support it. You see the reply being typed out word by word, similar to how ChatGPT works. Discord, Slack, and Telegram all support this. Twitch sends the final response as a complete message since IRC doesn't support message editing.

Webhook

The webhook adapter is for programmatic access — CI hooks, scripts, monitoring alerts, anything that can make an HTTP request.

curl -X POST http://localhost:18789/webhook \
  -H "Content-Type: application/json" \
  -d '{"message": "hello", "sender_id": "script", "conversation_id": "test"}'

Hot Reloading

Changes to bindings and permissions (channel filters, DM allowed users) take effect within a couple of seconds — no restart needed. Token and credential changes are applied by reconnecting the adapter.