NousResearch/hermes-agent
Feishu media attachment delivery bug and fixes
Cluster 10136 · gateway. Data as of
1 open item. Fix attempted, not merged.
The short answer
1open issue
0open PRs
11items grouped
- Known?
- Yes. 11 related items grouped here, 5 issues already closed.
- Fix event
- No fix has been merged to main. 5 PRs 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 0 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA cluster of bug reports, fixes, and tests all centered on media attachments (images, video, files) being silently dropped or not routed to the Feishu/Lark send_message pipeline. The core issue involves the media_files parameter not being passed through to the _send_feishu() function.
Open issues1
- Issue#18831[Feishu] send_message MEDIA attachments silently dropped; send_voice sends file attachment instead of native audio bubble
Open PRs0
5 PRs closed without merging
From the close comments: done elsewhere 4 · duplicate 1
-
#10392 fix: enable Feishu media delivery in send_message · done elsewhere →
cdde0c8 -
#14049 fix: route media files to Feishu send_message pipeline · done elsewhere →
cdde0c8,#10392 - #14365 fix(feishu): route send_message media attachments · duplicate
-
#14494 fix(send_message): pass media_files to _send_feishu in _send_to_platform · done elsewhere →
cdde0c8,#14365 -
#27373 test(feishu): add MEDIA attachment delivery coverage for send_message tool (closes #26876) · done elsewhere →
5600105
Closed issues · 5
- Closed#10136[Bug] Feishu file sending broken: media_files parameter not passed to _send_feishu()
- Closed#17418关于飞书端无法发送图片、DOCX 等附件的BUG
- Closed#18161Feishu: send_message MEDIA 图片发送不支持
- Closed#24906[Bug]: Feishu Plugin MEDIA Protocol Support Issue
- Closed#26876[Feishu] MEDIA:/path/ attachments silently stripped — files not delivered
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.15: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- gateway
- Closed issues
- 5
- Attempts
- 5 PRs closed without merging