OpenClaw suddenly doesn't reply to messages, many times it's not that the chat thread is broken, it's doing context compression, or there's something wrong with the gateway itself. OpenClaw's official open-source repository is https://github.com/openclaw/openclaw。 The official compaction documentation is clearly stated: when a session approaches the context limit, OpenClaw compresses the old message into a summary and retries the original request if necessary. The log page states that the first thing to look at when troubleshooting should be 'openclaw logs --follow', and if the gateway is unreachable, run 'openclaw doctor'. The related documents are compaction and logging, respectively.
First distinguish which kind of "no reply" is
Sometimes it actually goes back, just because the compaction compresses the old context and you feel broken; Sometimes, the gateway is stuck, the profile fails, or the model provider reports an error, resulting in no messages being sent at all. Both situations look like "silence", but the troubleshooting path is completely different.
You can do these three things first
- Run 'openclaw logs --follow' to see where the most recent request stopped.
- Run 'openclaw doctor' to confirm whether the Gateway and profile are healthy.
- For long sessions, try '/compact' or just start a new session to see if it's too context-heavy.
A lot of silence is actually normal behavior for long conversations. As long as the logs, gateway status, and compactions are sorted out first, most problems can be located.
