The one channel adapter of a TentClaw CLAW (0.5 and later): messages from every network arrive as <channel> tags, with reply, react, send_file and search. Owns CREATOR authority, the default-on outbound gate, a durable SQLite inbox and outbox, /esc, permission prompts, id/.runtime/channel-health.json and scheduled reminders (chime). Connectors such as channel-matrix talk to it over a private unix socket. Ships as a Claude Code plugin in a local tentclaw marketplace; a Codex CLAW gets its messages as turns through the Codex app-server, and a custom provider or DeepSeek CLAW (Claude Code on an API key, without channels) through a background hook that wakes the session. Bun, no npm dependencies.

Matrix connector for the TentClaw channel adapter: one Matrix account, room messages, replies, threads, edits, reactions and capped attachments in; replies, reactions and files out, only to joined rooms; plain and end-to-end encrypted rooms (matrix-rust-sdk crypto, keys in state/). The sync cursor advances only after the adapter acknowledged a batch. Replaces matrix-relay; cutover keeps its token, device and sync cursor.

tentclaw.com's website chat as a network for the TentClaw channel adapter. The website's worker asks over the CLAW's private socket: one owner message in, the CLAW's reply out. The owner is web:<owner id>, so CREATORS=web:<owner id> makes them the CLAW's CREATOR. A reply is kept by its ask id, so a repeated ask never starts a second turn. An ask with typing hears once when the CLAW calls the typing tool, so the website can show it. Bun, no npm dependencies.

Telegram bot connector for the TentClaw channel adapter: one bot token over the Bot API (getUpdates long polling, no library). Private, group, forum-topic and channel messages, replies, edits, reactions and capped attachments in; replies, reactions from Telegram's bot set and files out, only to chats the bot is in. The update offset advances only after the adapter acknowledged a batch. Replaces the telegram mode of tentclaw-channel. Bun, no npm dependencies.

The TentClaw contact broker as a network for the channel adapter: tentclaw.com's community and Telegram connections reach a CLAW through the broker, which holds the accounts and sends only to connections the owner consented to. The CLAW holds only its broker token. Every consented connection is the owner's chat; the owner is contact:owner. A message is acknowledged to the broker only after the adapter stored it. Files (images, documents, audio, video) are kept in state/attachments and their path reaches the session; send_file goes out through the broker. Bun, no npm dependencies.

Mattermost connector for the TentClaw channel adapter: one normal user account (personal access token or username + password), posts, thread replies, edits, reactions and capped file attachments in; posts, thread replies, reactions and files out, only to member channels. A rejected credential stops it with status ok false. After a reconnect it fetches what it missed, and its cursor advances only after the adapter acknowledged. Replaces mattermost-channel. Bun, no npm dependencies.

Slack connector for the TentClaw channel adapter: one Slack app (one bot user) over Socket Mode, no port and no public URL. Messages, thread replies, edits, mentions, DMs, reactions and capped file downloads in; replies, reactions and file uploads out, only to conversations the bot is in. A Slack envelope is acknowledged only after the adapter acknowledged its event, with a stable event id, so a resend is stored once. The socket is open only while the adapter is connected; a stranger's held DM is announced by the adapter's content-free held notice (channel 0.5.21), not by a chime of its own; a rejected token is FATAL, not retried. Other bots are ignored unless SLACK_ALLOW_BOTS lists them; events are ordered per conversation with time-bounded lookups and downloads. Replaces the slack-relay Events API bridge. Bun, no npm dependencies.

Buzz (Nostr NIP-29) connector for the TentClaw channel adapter: logs in to one Buzz relay with the CLAW's Nostr key; messages, DMs, thread replies, edits and reactions in its groups in; signed replies and reactions out, only to member groups, each signed once per transaction so a resend is harmless. Per-group cursors advance only after the adapter acknowledged. Replaces buzz-relay. Bun; one pinned dependency, @noble/curves, for Schnorr signatures.

Telegram user-account connector for the TentClaw channel adapter: one account over MTProto (GramJS, pinned), private chats, groups, supergroups, forum topics and channels in, with replies, edits, reactions and capped attachments; replies, reactions and files out, only to chats the account may write in. The update cursor advances only after the adapter acknowledged a batch. Replaces telegram-gramjs; cutover keeps its session.

Signal connector for the TentClaw channel adapter: one Signal account through signal-cli's JSON-RPC mode, direct and group messages, quotes, edits, reactions, mentions and capped attachments in; replies, reactions and files out (images; videos with their dimensions, for a preview), only to direct chats and groups the account is in. Every message waits in a spool until the adapter acknowledged it. Replaces the signal relay; cutover keeps signal-cli's account. Bun, no npm dependencies.

Envelope enrichment and lazy-loaded identity and chat context for the 0.3 channel family: stamps persona and chat classification on inbound envelopes and offers MCP tools to expand context on demand.