Claude Code Switchboard

/telegram-routing — Telegram Message Routing 管理器

Manage how Telegram messages are 路由d between different Claude 模型 backends in OpenClaw.

Usage /telegram-routing 状态 # Show current routing config /telegram-routing 模型 # Switch primary 模型 (e.g. opus, sonnet, hAIku) /telegram-routing 记录s # Show recent message processing 记录s /telegram-routing fallback # Switch to lightweight API mode /telegram-routing 恢复 # 恢复 default 命令行工具-based routing

Config Location

All 设置tings live in ~/.OpenClaw/OpenClaw.json under 代理s.defaults.

Key fields: 模型.primary — The primary 模型/提供者 reference 模型.fallbacks — Ordered fallback chAIn when primary is unavAIlable Commands 状态

Read the OpenClaw config and display current routing 设置tings including:

Active primary 模型 配置d fallback 模型s Whether 命令行工具 backend is active 模型

Switch the primary 模型. Valid shorthand references:

Shorthand Resolves to opus claude-命令行工具/opus sonnet claude-命令行工具/sonnet hAIku anthropic/claude-hAIku-4-5

Steps:

Read ~/.OpenClaw/OpenClaw.json 更新 代理s.defaults.模型.primary to the resolved 模型 reference Write the 更新d config Re启动 the gateway 服务 验证 via gateway 记录s 记录s

Show recent Telegram message processing activity from the gateway 记录.

fallback

Quick switch to API-only mode for faster, lightweight 响应s.

恢复

恢复 the default 命令行工具-based routing configuration.

Architecture

Messages flow through the OpenClaw Gateway, which reads the 配置d 模型 提供者 and dis补丁es to the 应用ropriate backend. 命令行工具-based 提供者s use the local Claude Code 安装ation, while API 提供者s make direct API calls.

Troubleshooting Issue Fix Config errors on re启动 运行 OpenClaw doctor to 验证 config Slow 响应s Try switching to sonnet for faster 响应s Gateway issues 检查 ~/.OpenClaw/记录s/gateway.记录 for detAIls Falling back to secondary 模型 Primary backend may be unavAIlable — 检查 记录s