Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Initially I upgraded from 2026.6.10 to 2026.6.11 and there were no issues. This morning, sessions started breaking for now reason. No changes were made. I create a new session, send a message. Model replies. I send a reply, and never get a response. The logs show the following:

07:28:10-07:00 error diagnostic {"subsystem":"diagnostic"} message dispatch completed: channel=discord sessionId=unknown sessionKey=agent:main:main source=replyResolver outcome=error duration=10ms error="Error: reply session initialization conflicted for agent:main:main"
07:28:10-07:00 error diagnostic {"subsystem":"diagnostic"} message processed: channel=discord chatId=user:408672255804047380 messageId=1521885130589995112 sessionId=cb95c985-9e3b-4d55-80e3-e43673fdac0d sessionKey=agent:main:main outcome=error duration=15ms error="Error: reply session initialization conflicted for agent:main:main"
07:28:12-07:00 error channels/discord {"subsystem":"channels/discord"} discord message run failed: Error: reply session initialization conflicted for agent:main:main
07:28:42-07:00 error diagnostic {"subsystem":"diagnostic"} message dispatch completed: channel=webchat sessionId=unknown sessionKey=agent:main:main source=replyResolver outcome=error duration=13ms error="Error: reply session initialization conflicted for agent:main:main"
07:28:42-07:00 error diagnostic {"subsystem":"diagnostic"} message processed: channel=webchat chatId=unknown messageId=556f73fd-4093-4a0e-9c73-16c7130893bc sessionId=cb95c985-9e3b-4d55-80e3-e43673fdac0d sessionKey=agent:main:main outcome=error duration=20ms error="Error: reply session initialization conflicted for agent:main:main"

Restarting the gateway and starting a new session fixes it temporarily and then it happens again. I've tried dmScope main and per-channel-peer. Nothing seems to resolve it.

I've tried different models, the results are the same.

Steps to reproduce

1. Upgrade to 2026.6.11.
2. At some point chat breaks.
3. Check logs, observe error.

Expected behavior

Chat should not break.

Actual behavior

Models stops responding.

OpenClaw version

2026.6.11

Operating system

Linux

Install method

docker

Model

gpt-5.5 with Codex

Provider / routing chain

openclaw -> codex -> gpt-5.5

Additional provider/model setup details

No response

Logs

07:28:10-07:00 error diagnostic {"subsystem":"diagnostic"} message dispatch completed: channel=discord sessionId=unknown sessionKey=agent:main:main source=replyResolver outcome=error duration=10ms error="Error: reply session initialization conflicted for agent:main:main"
07:28:10-07:00 error diagnostic {"subsystem":"diagnostic"} message processed: channel=discord chatId=user:408672255804047380 messageId=1521885130589995112 sessionId=cb95c985-9e3b-4d55-80e3-e43673fdac0d sessionKey=agent:main:main outcome=error duration=15ms error="Error: reply session initialization conflicted for agent:main:main"
07:28:12-07:00 error channels/discord {"subsystem":"channels/discord"} discord message run failed: Error: reply session initialization conflicted for agent:main:main
07:28:42-07:00 error diagnostic {"subsystem":"diagnostic"} message dispatch completed: channel=webchat sessionId=unknown sessionKey=agent:main:main source=replyResolver outcome=error duration=13ms error="Error: reply session initialization conflicted for agent:main:main"
07:28:42-07:00 error diagnostic {"subsystem":"diagnostic"} message processed: channel=webchat chatId=unknown messageId=556f73fd-4093-4a0e-9c73-16c7130893bc sessionId=cb95c985-9e3b-4d55-80e3-e43673fdac0d sessionKey=agent:main:main outcome=error duration=20ms error="Error: reply session initialization conflicted for agent:main:main"

Screenshots, recordings, and evidence

No response

Impact and severity

High, openclaw is effectively broken.

Additional information

No response