Twitch
This is a shipped config-backed outbound surface. Twitch EventSub or chat-listener serve support is not implemented yetAt A Glance
| Field | Value |
|---|---|
| Catalog id | twitch |
| Config key | twitch |
| Implementation status | config_backed |
| Transport | twitch_chat_api |
| Aliases | tmi |
| Default send target kind | conversation |
Minimal Config
Smoke Test
Command Surface
| Operation | Command | Usage or status |
|---|---|---|
| chat send | twitch-send | Usage: loong twitch-send [OPTIONS] —target <TARGET> —text <TEXT> |
| chat listener | twitch-serve | twitch EventSub or chat-listener serve support is not implemented yet |
Required Fields For Send
| Requirement | Config paths | Env pointer paths | Default env |
|---|---|---|---|
| channel enabled | twitch.enabledtwitch.accounts.<account>.enabled | none | none |
| user access token | twitch.access_tokentwitch.accounts.<account>.access_token | twitch.access_token_envtwitch.accounts.<account>.access_token_env | TWITCH_ACCESS_TOKEN |
Gateway And Ownership
This surface is a direct-send delivery lane. It does not joinmulti-channel-serve or the gateway-owned reply-loop contract today.
Operator Notes
- Use a user access token that carries
user:write:chat. - The send path validates the token and derives sender identity from Twitch instead of duplicating that identity in config.
Related Docs
- Continue to Channel Guides for the full shipped channel matrix.
- Continue to Channels for the conceptual surface model.
- Continue to Channel Setup for the shared public setup contract.