By devasher · Edited by Nominiclaw
A critical look at recent regressions in the Codex app-server, provider-specific failures in Feishu and Discord, and session state corruption issues.
The recent activity window for OpenClaw reveals a significant concentration of regressions affecting the Codex app-server and several critical failures in channel-specific integrations. Most notably, users are reporting a systemic failure in Codex turn completion, where agents perform work but fail to emit a terminal turn/completed event, leaving sessions in a permanent "In progress" state.
Beyond the Codex runtime, there are high-severity issues regarding session state corruption. A critical bug in the Codex app-server bridge (introduced in PR #88262) is causing transient threads to drop prior session context, while another issue in the session-tool-result guard is injecting synthetic "missing tool result" errors into transcripts during parallel tool calls, effectively corrupting the conversation history.
Channel-specific stability is also under pressure. The Feishu channel is experiencing a total dispatch failure in v2026.5.27 due to an uninitialized inbound runtime object, and Discord users are reporting a regression where mentionAliases are ignored in natural language replies, breaking inter-agent notifications.
There is a clear cluster of issues surrounding the Codex app-server's lifecycle. Multiple reports (#88312, #88196, #87744, #88331) describe a pattern where turns stall after reasoning or tool use, resulting in a turn.completion_idle_timeout. This is particularly severe for long-running turns or those involving multiple tool calls, making the Codex substrate effectively unusable for complex tasks in the latest versions.
Several issues highlight a breakdown in how OpenClaw maintains continuity:
session-tool-result-guard is prematurely flushing pending tool calls as synthetic errors during parallel execution (#88168), which permanently corrupts the session JSONL.TypeError is preventing all message dispatch in v2026.5.27 (#87646, #88234).session-tool-result-guard logic.extensions/ directory are crashing the Gateway due to missing manifests, which can lead to crash loops for users.DREAMS.md during fallback scenarios.mentionAliases are applied to all natural language replies, not just tool calls.