What problem does it solve? When you switch an AI gateway's model or receive a new API key, the gateway can silently fall back to an old model without any visible error, leaving you running the wrong model for days. This playbook walks through verifying keys, updating configuration, restarting the gateway, and confirming the actual model in use. ## Core Features & Use Cases - Telegram message mangling awareness: Explains how Telegram inserts spaces into API keys and masks IP addresses, and how to recover the original text before validating. - End-to-end model switch procedure: Validate the key against /v1/models, set config via the hermes CLI (config.yaml is locked against direct edits), restart the gateway via a scheduled script, and verify the real model from the sessions table. - Silent fallback diagnosis: Query state.db to see which model actually ran, test the primary key directly, and fix model_not_found or 401 failures. - Use Case: A user reports the backend shows deepseek even though glm was configured. Follow the playbook to discover the key was corrupted by Telegram whitespace, re-validate it, update config, restart via an at-scheduled script, and confirm the new model in recent sessions. ## Quick Start Use the model-switch-playbook to switch the gateway to the glm model with this API key and verify which model is actually running.