OpenClaw Session Reply Debug & Model Fallback

Diagnose OpenClaw "message sent but no assistant reply" issues, then safely switch active model references with primary + multi-fallback support, including h...

This skill appears coherent and does what it claims, but exercise normal caution before applying changes: 1) Run the scripts without --apply first (dry-run) to see planned edits. 2) Inspect the generated backups (.bak.<timestamp>) before overwriting. 3) Review openclaw.json and ensure provider.baseUrl is the expected upstream and you trust that endpoint — the scripts will use the apiKey stored there to perform probe requests. 4) If you plan to run via heartbeat/cron, verify the exact command the cron will run and that you want automatic periodic re-probing and potential reconfiguration. 5) Only run --apply on machines you control and have backups of your OpenClaw data if you need to be extra cautious.

Type: OpenClaw Skill Name: openclaw-session-reply-debug Version: 1.0.1 The skill bundle provides legitimate tools for diagnosing OpenClaw connectivity issues and managing model fallbacks. The included Node.js scripts (switch-model-with-fallback.js and switch-model-to-gpt-5.2.js) perform targeted configuration updates and connectivity probes using the user's own configured API endpoints and keys. While the scripts interact with sensitive configuration files and perform network requests, their behavior is transparent, includes safety features like file backups, and is strictly aligned with the stated purpose of model recovery and automated switching via OpenClaw's heartbeat mechanism.