Twitch

This is a shipped config-backed outbound surface. Twitch EventSub or chat-listener serve support is not implemented yet

At A Glance

[twitch]
enabled = true
access_token_env = "TWITCH_ACCESS_TOKEN"

loong channels send twitch --target "example_channel" --text "hello from loong"

Operation	Command	Usage or status
chat send	`channels send twitch`	Usage: loong channels send twitch [OPTIONS] —target <TARGET> —text <TEXT>
chat listener	`channels serve twitch`	twitch EventSub or chat-listener serve support is not implemented yet

Requirement	Config paths	Env pointer paths	Default env
channel enabled	`twitch.enabled` `twitch.accounts.<account>.enabled`	none	none
user access token	`twitch.access_token` `twitch.accounts.<account>.access_token`	`twitch.access_token_env` `twitch.accounts.<account>.access_token_env`	`TWITCH_ACCESS_TOKEN`

This surface is a direct-send delivery lane. It does not join gateway run or the gateway-owned reply-loop contract today.

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.