Manage how OpenClaw routes Telegram messages to different Claude model backends. Switch between CLI and API providers with simple config changes.
Manage how Telegram messages are routed between different Claude model backends in OpenClaw.
/telegram-routing status # Show current routing config
/telegram-routing model <ref> # Switch primary model (e.g. opus, sonnet, haiku)
/telegram-routing logs # Show recent message processing logs
/telegram-routing fallback # Switch to lightweight API mode
/telegram-routing restore # Restore default CLI-based routing
All settings live in ~/.openclaw/openclaw.json under agents.defaults.
model.primary — The primary model/provider referencemodel.fallbacks — Ordered fallback chain when primary is unavailableRead the OpenClaw config and display current routing settings including:
Switch the primary model. Valid shorthand references:
| Shorthand | Resolves to |
|---|---|
opus | claude-cli/opus |
sonnet | claude-cli/sonnet |
haiku | anthropic/claude-haiku-4-5 |
Steps:
~/.openclaw/openclaw.jsonagents.defaults.model.primary to the resolved model referenceShow recent Telegram message processing activity from the gateway log.
Quick switch to API-only mode for faster, lightweight responses.
Restore the default CLI-based routing configuration.
Messages flow through the OpenClaw Gateway, which reads the configured model provider and dispatches to the appropriate backend. CLI-based providers use the local Claude Code installation, while API providers make direct API calls.
| Issue | Fix |
|---|---|
| Config errors on restart | Run openclaw doctor to validate config |
| Slow responses | Try switching to sonnet for faster responses |
| Gateway issues | Check ~/.openclaw/logs/gateway.log for details |
| Falling back to secondary model | Primary backend may be unavailable — check logs |
ZIP package — ready to use