Skip to main content

​
Channels

Connect your agents to messaging platforms. Users on those platforms chat with your agents directly — all from one app, running simultaneously.
All incoming messages are scanned for prompt injection — messages with critical severity are blocked automatically.

​
Supported channels

Telegram

Bot API — public bots, group chats

Discord

Gateway WebSocket — community servers

Slack

Bot API — workplace teams

Matrix

Client-Server API — decentralized chat

IRC

IRC protocol — classic chat rooms

Mattermost

WebSocket API — self-hosted teams

Nextcloud

Talk API — Nextcloud users

Nostr

NIP relay protocol — decentralized social

Twitch

IRC + API — live streaming chat

Webchat

HTTP/WebSocket — your own website

WhatsApp

Evolution API — personal & group messaging

​
How channels work

​
DM policies

Control who can message your agents:
PolicyBehavior
OpenAnyone can chat
AllowlistOnly approved users
PairingUsers must pair with a code

​
Channel routing

Route messages to specific agents based on rules:
  1. Go to Settings → Channels
  2. Add routing rules with filters:
    • Channel — which platform
    • User filter — specific users
    • Channel ID filter — specific channels/groups
    • Agent — which agent handles it
Rules are evaluated first-match-wins — the first matching rule determines the agent.

​
Security

  • All incoming messages are scanned for prompt injection
  • Messages with critical severity are blocked automatically
  • Each user gets an isolated session (no cross-user contamination)
  • Access control is per-channel and per-user
  • Channel agents use worker_model by default (cheaper, faster)

​
Lean channel context

Channel bridges use a minimal context strategy optimized for speed and low token cost:
  • Core identity only — the agent loads its identity, soul, and user files, but skips the full agent context (other agents, all tools, custom files)
  • No memory recall overhead — memory search (BM25 + vector) is skipped for channel messages to reduce latency. Memory is still available on-demand via the memory_search tool if the agent needs it.
  • Minimal tool set — channel agents only get the tools relevant to that bridge (~4 tools), not the full 25,000+ integration catalog
  • Worker model — channels default to worker_model (cheaper/faster) rather than the boss model
This means a channel message costs a fraction of a full chat turn. An agent responding on Discord or Telegram uses ~2K–4K tokens of context instead of ~10K–30K for a full desktop chat. Over thousands of channel messages, this saves significantly on token costs. :::tip If you need a channel agent to have full capabilities (memory recall, all tools), configure it as a dedicated agent with a larger context window and full tool access in Settings → Agents. :::

​
Provider fallback

If the primary provider fails (billing, auth, or rate limit errors), Pawz automatically tries other configured providers before failing.