snowclaw channel
Manage messaging channels the agent can reach — Slack, Telegram, Discord. Channel credentials become individual Snowflake secrets, and network rules for each channel's hosts are auto-detected.
Supported channels
| Channel | Auth | Notes |
|---|---|---|
| Slack | Bot token + app token | Socket mode — no public webhook needed |
| Telegram | Bot token + user ID | Allowlist-based via allowFrom |
| Discord | Bot token | Optional guild-based filtering |
list
snowclaw channel list
Shows configured channels, their IDs, and the credentials each one expects. Credentials themselves live in .env (values are not printed).
add
snowclaw channel add
Interactive wizard:
- Pick a channel type (Slack, Telegram, or Discord).
- Enter credentials — the wizard marks each as either a secret (goes to
.envand SnowflakeSECRET) or inline (goes directly intoopenclaw.json). - Fill in any extra config (e.g. Telegram
allowFromuser ID, Discord guild allowlist). - The CLI auto-detects required network rules for that channel (e.g.
api.telegram.org:443) and offers to apply them.
After adding, the CLI nudges you to redeploy so SPCS picks up the new secrets and network rules.
edit
snowclaw channel edit <name>
Re-opens the credential prompts for an existing channel. Use this to rotate tokens or update an inline config value.
remove
snowclaw channel remove <name>
Removes a channel from openclaw.json, clears its .env entries, and (optionally) drops the associated Snowflake SECRET objects. Network rules tied only to the removed channel can be dropped via snowclaw network remove.