Bug: Assistant response delivered to Discord but not persisted to session file

Version: OpenClaw 2026.5.2

Summary

An assistant response was successfully delivered to Discord (visible in chat, confirmed in gateway logs), but was NOT persisted to the session JSONL file. This caused the assistant to lose context — it couldn't recall its own response from 2 minutes prior when the user replied.

Environment

• OpenClaw: 2026.5.2 (stable, npm/pnpm)
• OS: Linux 6.17.0-1014-nvidia (arm64)
• Model: vllm/qwen3.6-fp8 (262k context)
• Channel: Discord (private channel)

Evidence

Gateway log — response delivered at 13:14:03 Berlin (11:14:03 UTC):

• date: 2026-05-03T11:14:03.185Z
• status: 200
• method: POST /channels/1484297866708254741/messages
• x-ratelimit-limit: 5

Session file (62d055ee-889d-42b2-8fa2-946cb9b48bb7.jsonl) — NO assistant entry at 11:14 UTC:

• Line 51: 2026-05-03T11:13:29Z (user message)
• Line 53: 2026-05-03T11:15:43Z (next user message)
• Missing: Assistant response between 11:13 and 11:15 UTC

Compaction was NOT involved: Session had only ~40k estimated tokens with a 262k context window. No compaction markers in file.

Root Cause

The response was sent to Discord and confirmed (HTTP 200), but the corresponding entry was never written to the session JSONL file. This is a persistence/recording failure in the session recording pipeline, NOT a compaction or context window issue.

Impact

• User sees assistant response in Discord
• Assistant loses awareness of its own response
• When user replies referencing that response, assistant appears to have "lost context"
• Damages conversation continuity and trust

Expected Behavior

Every assistant response delivered to a channel should be persisted to the session file.