Pop!_OS 出现空白回复/挂起时的分层排障手册
针对‘日志显示 run done 但聊天气泡为空’问题,社区案例给出可执行排障顺序:先鉴权与配额,再模型映射,再 provider 最小化回归。
REDDITDiscovered 2026-02-12Author u/skywave84
Prerequisites
- You can run gateway in verbose mode and inspect provider status.
- At least one known-good API key/model pair is available for A/B test.
Steps
- Capture baseline with one failing prompt and collect logs from run start to run done.
- Validate auth and quota per provider (`models status`) before changing model IDs.
- Reduce to one provider + one model, then test web chat and TUI separately.
- If logs show success but UI empty, inspect renderer/output parsing path and compare with known-good release.
- Only after root-cause is clear, re-introduce fallback providers one by one.
Commands
openclaw gateway statusopenclaw helpopenclaw gateway restartVerify
`test` prompt returns non-empty content in both web and TUI for 10 consecutive runs.
Caveats
- Case combines multiple providers and may include account-specific limits; reproduce in your environment first(需验证).
- Do not rotate all providers at once, or you lose causality in troubleshooting.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗