Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] Inbound metadata JSON still rendered to Discord chat output (v2026.5.20)

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…

The Discord bridge continues to render inbound untrusted metadata JSON blocks directly into chat output. These blocks are visible to all users in Discord DMs and channels.

Root Cause

The Discord bridge continues to render inbound untrusted metadata JSON blocks directly into chat output. These blocks are visible to all users in Discord DMs and channels.

Code Example

{
  "chat_id": "user:930087641553207376",
  "message_id": "1509503400193032192",
  "sender_id": "930087641553207376",
  "sender": "User Name",
  "timestamp": "Thu 2026-05-28 17:27 GMT+7",
  "inbound_event_kind": "user_request"
}

---

{
  "label": "User Name (930087641553207376)",
  "id": "930087641553207376",
  "name": "User Name",
  "username": "username",
  "tag": "username"
}
RAW_BUFFERClick to expand / collapse

Description

The Discord bridge continues to render inbound untrusted metadata JSON blocks directly into chat output. These blocks are visible to all users in Discord DMs and channels.

What users see

{
  "chat_id": "user:930087641553207376",
  "message_id": "1509503400193032192",
  "sender_id": "930087641553207376",
  "sender": "User Name",
  "timestamp": "Thu 2026-05-28 17:27 GMT+7",
  "inbound_event_kind": "user_request"
}
{
  "label": "User Name (930087641553207376)",
  "id": "930087641553207376",
  "name": "User Name",
  "username": "username",
  "tag": "username"
}

Expected

These metadata blocks should be internal-only and not rendered to chat output.

Environment

  • OpenClaw version: 2026.5.20 (e510042)
  • Channel: Discord
  • Mode: Direct messages + channel messages

Related

PR #50520 attempts to fix this but issue persists on v2026.5.20.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING