DingTalk media, file, and messaging delivery issues

NousResearch/hermes-agent · cluster 9149 · gateway

Data as of

10 open items. Fix attempted, not merged.

The short answer

8open issues
2open PRs
16items grouped
Known?
Yes. 16 related items grouped here, 4 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
8 issues and 2 PRs.

These issues and PRs concern the DingTalk adapter's handling of file and image sending/receiving, inbound file dispatch via stream callbacks, webhook expiry, and proactive/cross-platform message delivery failures. The members share a common focus on gaps and bugs in DingTalk media support and message routing.

Open issues8

  • Issue#11966Dingtalk Stream Mode: send_message to chat_id fails (expects webhook config) even though stream is active
  • Issue#13463[Feature] Add File and Image Interaction Support for DingTalk Channel
  • Issue#22487[Bug]: DingTalk: Cannot send image and files via gateway
  • Issue#23513bug(dingtalk): session_webhook expires silently within same Stream Mode connection, causing message delivery failures
  • Issue#30144DingTalk sampleFile returns "robot 不存在" (robot not found) for internal apps
  • Issue#31643DingTalk adapter does not support MEDIA/local file attachments
  • Issue#40818DingTalk proactive messaging does not work — cron notifications and cross-platform send_message always fail
  • Issue#65011DingTalk Gateway: Support file reception (like OpenClaw)

Open PRs2

  • PR#23575fix(gateway): warn before DingTalk session_webhook expires in long-lived stream
  • PR#23612fix(dingtalk): support native local media replies

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #17230 fix(dingtalk): extract and resolve download code for file/audio/video callbacks (#16964) · superseded by another PR → 2c75c83
  • #33642 feat(dingtalk): implement image/file upload and inbound file download · merged via another change
Closed issues · 4
  • Closed#9149[DingTalk] Add file/image sending support and fix 5 bugs in DingTalk adapter
  • Closed#16964[Bug]: DingTalk: file/document messages received via stream CALLBACK never reach inbound dispatcher (PDF/DOCX silently dropped)
  • Closed#21462[Feature]: The DingTalk channel connector can't send image,when will the funtion be supported ?
  • Closed#30143DingTalk sampleFile returns "robot 不存在" (robot not found) for internal apps
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.11: 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
4
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.