OpenClaw's Tlon integration picked up a reliability fix for a classic parser edge case. Merged PR #130048 updates the Tlon Urbit Server-Sent Events client so it accepts legal data: and id: fields even when there is no space after the colon.
That sounds tiny, but the failure mode was not. The PR explains that the previous parser accepted only data: and id: with a space. The SSE standard allows the space to be omitted, so valid frames such as data:{...} and id:20 could be mishandled.
The Failure Mode
Before this change, a no-space data:{...} line could leave the parsed data field empty. OpenClaw would then return before dispatching the event. The PR says this could make messages, reactions, notifications, and settings events disappear without an error.
The id:20 case was different but still damaging. The payload could dispatch, but the event ID would remain empty, preventing the client from advancing and sending its acknowledgement.
In practical terms, Tlon rooms could see valid events vanish or remain unacknowledged simply because an upstream SSE frame used a valid compact form.
The Fix
The implementation keeps the repair inside the Tlon-owned SSE parser. Instead of matching the full spaced prefix, it matches the SSE field names:
id:data:
The parser then trims the parsed field value before passing it to the existing Urbit payload and event-ID handling. This keeps the behavior aligned with the standard while avoiding a broader routing or channel-layer rewrite.
The PR is marked P1, which fits the impact. Dropped room events are exactly the sort of problem that can make a chat integration feel unreliable even when the underlying connection is alive.
Validation
The evidence in the PR includes a direct reproduction on current main before the fix. A focused test using id:20 and data:{...} failed because the handler was not called. The full pre-fix two-file run also failed parser assertions and timed out in the loopback transport test because the no-space frame was never delivered.
After the repair, the exact focused command passed 37 tests across two Tlon SSE files. The parser test checks both handler delivery and the outgoing acknowledgement body, while the loopback test sends a no-space event stream over real HTTP and verifies owner-driven close.
The PR also lists collateral Telegram smoke proof, but it explicitly says that Telegram does not exercise the Tlon Urbit SSE behavior. That distinction is useful: the Tlon fix stands on the parser and loopback evidence, not on unrelated channel success.
Bottom Line
For OpenClaw users running Tlon or Urbit-backed rooms, this should reduce silent event loss from standards-compliant SSE producers. It is a one-line production repair with focused tests, and it closes a real reliability gap in channel ingress.