[codex] Fix OpenClaw gateway v4 and emoji display handling#1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Updated Listener for the latest OpenClaw Gateway protocol and kept emoji-display working even when speaker playback is disabled.
Why
The recent OpenClaw update moved Gateway clients to protocol v4. Listener still used protocol v3 in both its input-side and speaker-side Gateway clients, which caused websocket compatibility failures. While fixing that, we also decoupled emoji-display delivery from TTS playback so emoji still show when speaker is turned off.
Impact
Validation