WeCom inbound image/media extraction bugs and fixes

NousResearch/hermes-agent · cluster 11495 · gateway

Data as of

2 open items. Fix attempted, not merged.

The short answer

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

A cluster of bug reports and corresponding fixes addressing WeCom's failure to extract inbound image and media attachments, including image_key handling, silent drop behavior, and state persistence issues.

Open issues2

  • Issue#11495[BUG] WeCom AI Bot: inbound image messages not extracted (extracted_media=0 despite image_keys present)
  • Issue#61762[Bug]: Unable to perceive when uploading pictures on Wecom

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: other 2

  • #11498 fix(wecom): extract inbound images delivered as image_keys (fixes extracted_media=0) · other
  • #61782 fix(wecom): handle image/file messages that fail media extraction without silent drop · other → #61762, #11495
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.39: 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
2 PRs closed without merging

For your agent

The same facts, typed.