Cairn
NousResearch/hermes-agent

Google Chat placeholder leak in nested markdown formatting

Cluster 128985 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These issues and PRs concern a bug where GCn placeholders are exposed in Google Chat messages when inline code appears inside bold, header, or link formatting. The fixes address restoring placeholders in the correct order (outermost-first) to handle nested markdown safely.

Open issues1

  • Issue#128985google_chat: format_message leaks GCn placeholders when inline code is inside bold/header/link text

Open PRs1

  • PR#128986fix(google-chat): restore nested markdown placeholders safely

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #129159 fix(google_chat): restore placeholders outermost-first (#128985) · superseded by another PR → #128986
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/128985.json
cluster/128985.md