openclaw - 💡(How to fix) Fix [Bug]: OpenClaw fails to relay messages from openai/gpt-5.5

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Upon configuring for ChatGPT and switching the primary model, OpenAI wasn't relaying the model's communications to me, only internal acknowledgments of it's functionality.

Root Cause

**Me:** Hello!
**OpenClaw:** Sent.
**Me:** Sent what?
**OpenClaw:** Clarified.
**Me:** I'm receiving no responses from you, other than single word communications. Explain.
**OpenClaw:** Delivered visible explanation.
**Me:** You absolutely did not. There was nothing visible about your explanation. Troubleshoot this OpenClaw implementation and find out why.
**OpenClaw:** Root cause found and patched locally.

Fix Action

Fix / Workaround

**Me:** Hello!
**OpenClaw:** Sent.
**Me:** Sent what?
**OpenClaw:** Clarified.
**Me:** I'm receiving no responses from you, other than single word communications. Explain.
**OpenClaw:** Delivered visible explanation.
**Me:** You absolutely did not. There was nothing visible about your explanation. Troubleshoot this OpenClaw implementation and find out why.
**OpenClaw:** Root cause found and patched locally.

Patch applied:                                                                                                                                                            
- Changed the filter to hide only messages where __openclaw.display === false.                                                                                            
- Patched /home/ec2-user/.npm-global/lib/node_modules/openclaw/dist/control-ui/assets/index-BsIpAbsh.js.                                                                  
- Added /home/ec2-user/.npm-global/lib/node_modules/openclaw/dist/control-ui/assets/index-BsIpAbsh-webchatfix.js.                                                         
- Updated /home/ec2-user/.npm-global/lib/node_modules/openclaw/dist/control-ui/index.html to load the cache-busted bundle.

You’ll likely need a hard refresh because the old asset may be cached by the service worker. This is a local package patch and may be overwritten by an OpenClaw update;  
the upstream fix belongs in the WebChat history filter.                                                                                                                   
 connected | idle                                                                                                                                                         
 agent main | session main | openai-codex/gpt-5.5 | tokens 37k/272k (14%)

Code Example

**Me:** Hello!
**OpenClaw:** Sent.
**Me:** Sent what?
**OpenClaw:** Clarified.
**Me:** I'm receiving no responses from you, other than single word communications. Explain.
**OpenClaw:** Delivered visible explanation.
**Me:** You absolutely did not. There was nothing visible about your explanation. Troubleshoot this OpenClaw implementation and find out why.
**OpenClaw:** Root cause found and patched locally.                                                                                                                                     
                                                                                                                                                                          
What happened:                                                                                                                                                            
- The message tool did create the longer replies. I verified they exist in agent:main:main history as delivery-mirror assistant messages.                                 
- WebChat’s frontend history filter was dropping any message with __openclaw metadata.                                                                                    
- The backend currently attaches __openclaw metadata to normal transcript messages, so the frontend dropped the real mirrored replies and only showed the live Codex final
  text: “Sent. / “Clarified.                                                                                                                                            
                                                                                                                                                                          
Patch applied:                                                                                                                                                            
- Changed the filter to hide only messages where __openclaw.display === false.                                                                                            
- Patched /home/ec2-user/.npm-global/lib/node_modules/openclaw/dist/control-ui/assets/index-BsIpAbsh.js.                                                                  
- Added /home/ec2-user/.npm-global/lib/node_modules/openclaw/dist/control-ui/assets/index-BsIpAbsh-webchatfix.js.                                                         
- Updated /home/ec2-user/.npm-global/lib/node_modules/openclaw/dist/control-ui/index.html to load the cache-busted bundle.                                                
                                                                                                                                                                          
You’ll likely need a hard refresh because the old asset may be cached by the service worker. This is a local package patch and may be overwritten by an OpenClaw update;  
the upstream fix belongs in the WebChat history filter.                                                                                                                   
 connected | idle                                                                                                                                                         
 agent main | session main | openai-codex/gpt-5.5 | tokens 37k/272k (14%)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Upon configuring for ChatGPT and switching the primary model, OpenAI wasn't relaying the model's communications to me, only internal acknowledgments of it's functionality.

Steps to reproduce

  1. Purchased ChatGPT subscription.
  2. Used openclaw config set model openai/gpt-5.5 command.
  3. Restarted gateway.
  4. Launched via openclaw tui command.

Expected behavior

Actually receiving communications from the LLM

Actual behavior

As seen in the below logs, openclaw really thought it was sending me responses. Instead, it was only convey its internal thinking. Upon telling it to troubleshoot and fix it, it had to modify OpenClaw.

OpenClaw version

OpenClaw 2026.5.19 (a185ca2)

Operating system

AWS Linux 2023

Install method

Via the command line on the website.

Model

openai/gpt-5.5

Provider / routing chain

openclaw -> openai/gpt-5.5

Additional provider/model setup details

No response

Logs, screenshots, and evidence

**Me:** Hello!
**OpenClaw:** Sent.
**Me:** Sent what?
**OpenClaw:** Clarified.
**Me:** I'm receiving no responses from you, other than single word communications. Explain.
**OpenClaw:** Delivered visible explanation.
**Me:** You absolutely did not. There was nothing visible about your explanation. Troubleshoot this OpenClaw implementation and find out why.
**OpenClaw:** Root cause found and patched locally.                                                                                                                                     
                                                                                                                                                                          
What happened:                                                                                                                                                            
- The message tool did create the longer replies. I verified they exist in agent:main:main history as delivery-mirror assistant messages.                                 
- WebChat’s frontend history filter was dropping any message with __openclaw metadata.                                                                                    
- The backend currently attaches __openclaw metadata to normal transcript messages, so the frontend dropped the real mirrored replies and only showed the live Codex final
  text: “Sent.” / “Clarified.”                                                                                                                                            
                                                                                                                                                                          
Patch applied:                                                                                                                                                            
- Changed the filter to hide only messages where __openclaw.display === false.                                                                                            
- Patched /home/ec2-user/.npm-global/lib/node_modules/openclaw/dist/control-ui/assets/index-BsIpAbsh.js.                                                                  
- Added /home/ec2-user/.npm-global/lib/node_modules/openclaw/dist/control-ui/assets/index-BsIpAbsh-webchatfix.js.                                                         
- Updated /home/ec2-user/.npm-global/lib/node_modules/openclaw/dist/control-ui/index.html to load the cache-busted bundle.                                                
                                                                                                                                                                          
You’ll likely need a hard refresh because the old asset may be cached by the service worker. This is a local package patch and may be overwritten by an OpenClaw update;  
the upstream fix belongs in the WebChat history filter.                                                                                                                   
 connected | idle                                                                                                                                                         
 agent main | session main | openai-codex/gpt-5.5 | tokens 37k/272k (14%)

Impact and severity

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Actually receiving communications from the LLM

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING