fallow acorn
Hey! My agent (Opus 4.6) doesn't reliably respond to system notifications. Here's what's happening:
I start Codex CLI in background (exec with background:true, pty:true)
When Codex finishes, the system notification "Exec completed (session-id, code 0)" arrives correctly in the session
The agent does NOT generate a response — it stays silent
Same issue with cron jobs (sessionTarget: "main", payload.kind: "systemEvent") — events arrive but the agent doesn't reply
Context is typically high at that point (well above the contextTokens limit, pruning active, compaction.mode: "safeguard"). Could it be that system events at high context get dropped or aren't treated as turn triggers?
Setup: OpenClaw 2026.2.2-3, compaction.mode: "safeguard", contextPruning.mode: "cache-ttl", memoryFlush.enabled: true, contextTokens: 16000.
Is there a way to ensure the agent ALWAYS generates a response to system events? Or should I use a different approach (e.g. isolated session cron instead of main session systemEvent)?