channels

`remoteclaw channels`

Manage chat channel accounts and their runtime status on the Gateway.

Related docs:

Channel guides: Channels
Gateway configuration: Configuration

Common commands

remoteclaw channels list
remoteclaw channels status
remoteclaw channels capabilities
remoteclaw channels capabilities --channel discord --target channel:123
remoteclaw channels resolve --channel slack "#general" "@jane"
remoteclaw channels logs --channel all

Add / remove accounts

remoteclaw channels add --channel telegram --token <bot-token>
remoteclaw channels add --channel nostr --private-key "$NOSTR_PRIVATE_KEY"
remoteclaw channels remove --channel telegram --delete

Tip: remoteclaw channels add --help shows per-channel flags (token, private key, app token, signal-cli paths, etc).

When you run remoteclaw channels add without flags, the interactive wizard can prompt:

account ids per selected channel
optional display names for those accounts
Bind configured channel accounts to agents now?

If you confirm bind now, the wizard asks which agent should own each configured channel account and writes account-scoped routing bindings.

You can also manage the same routing rules later with remoteclaw agents bindings, remoteclaw agents bind, and remoteclaw agents unbind (see agents).

When you add a non-default account to a channel that is still using single-account top-level settings (no channels.<channel>.accounts entries yet), RemoteClaw moves account-scoped single-account top-level values into channels.<channel>.accounts.default, then writes the new account. This preserves the original account behavior while moving to the multi-account shape.

Routing behavior stays consistent:

Existing channel-only bindings (no accountId) continue to match the default account.
channels add does not auto-create or rewrite bindings in non-interactive mode.
Interactive setup can optionally add account-scoped bindings.

If your config was already in a mixed state (named accounts present, missing default, and top-level single-account values still set), run remoteclaw doctor --fix to move account-scoped values into accounts.default.

remoteclaw channels login --channel whatsapp
remoteclaw channels logout --channel whatsapp

Troubleshooting

Run remoteclaw status --deep for a broad probe.
Use remoteclaw doctor for guided fixes.
remoteclaw channels list prints Claude: HTTP 403 ... user:profile → usage snapshot needs the user:profile scope. Use --no-usage, or provide a claude.ai session key (CLAUDE_WEB_SESSION_KEY / CLAUDE_WEB_COOKIE), or re-auth via Claude Code CLI.
remoteclaw channels status falls back to config-only summaries when the gateway is unreachable. If a supported channel credential is configured via SecretRef but unavailable in the current command path, it reports that account as configured with degraded notes instead of showing it as not configured.

Capabilities probe

Fetch provider capability hints (intents/scopes where available) plus static feature support:

remoteclaw channels capabilities
remoteclaw channels capabilities --channel discord --target channel:123

Notes:

--channel is optional; omit it to list every channel (including extensions).
--target accepts channel:<id> or a raw numeric channel id and only applies to Discord.
Probes are provider-specific: Discord intents + optional channel permissions; Slack bot + user scopes; Telegram bot flags + webhook; Signal daemon version; Microsoft Teams app token + Graph roles/scopes (annotated where known). Channels without probes report Probe: unavailable.

Resolve names to IDs

Resolve channel/user names to IDs using the provider directory:

remoteclaw channels resolve --channel slack "#general" "@jane"
remoteclaw channels resolve --channel discord "My Server/#support" "@someone"
remoteclaw channels resolve --channel matrix "Project Room"