feat(dingtalk): add proactive message API to send_message tool

[shuans]

send_message now supports sending to arbitrary DingTalk groups/users without requiring a webhook_url configuration. Uses the enterprise robot proactive message API (v1.0) when DINGTALK_CLIENT_ID and DINGTALK_CLIENT_SECRET are available.

Three-tier routing priority:

1. Proactive API — calls /v1.0/robot/groupMessages/send (groups) or /v1.0/robot/oToMessages/batchSend (users) with access_token. chat_id is respected. Requires "robot proactive message" permission.
2. Session webhook — looks up cached session webhook from recent inbound message (bot must have been @mentioned within ~5 minutes).
3. Static webhook — falls back to DINGTALK_WEBHOOK_URL (default group only; chat_id ignored).

Also adds module-level shared session webhook cache (get_dingtalk_session_webhook) so the send_message tool can access session webhooks cached by the gateway adapter.

Changes:

• gateway/platforms/dingtalk.py: Add shared cache + getter/storer functions; make adapter use shared cache; simplify _on_message store logic.
• tools/send_message_tool.py: Rewrite _send_dingtalk() with proactive API support, session webhook lookup, and improved error messages.

User-facing:

• hermes send_message dingtalk:cidXXXX "msg" # sends to specific group
• hermes send_message dingtalk:user123 "msg" # sends to specific user
• Requires DINGTALK_CLIENT_ID/SECRET (and optional DINGTALK_ROBOT_CODE).
• webhook_url optional now; default-group-only fallback still supported.

What does this PR do?

Related Issue

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

How to Test

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform:

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

• This skill is broadly useful to most users (if bundled) — see Contributing Guide
• SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
• No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
• I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs

[alt-glitch]

Overlaps significantly with #14336 (proactive messaging via Robot OpenAPI) and #12769 (proactive messaging + media pipeline). Recommend consolidating.

[shuans]

Hi guys, I built a CLI tool that sends messages directly to DingTalk (individual or group), with a plugin system so more platforms can be added later.
npx msgcli send "hello world"

[teknium1]

Thanks for the proactive DingTalk delivery work. The capability is still needed: current main returns No valid session_webhook when live sends lack an inbound webhook (plugins/platforms/dingtalk/adapter.py:847-856) and its standalone sender only uses a static webhook (plugins/platforms/dingtalk/adapter.py:1527-1562).

Problems

• The PR targets the retired inline adapter path. Commit 560010547 moved DingTalk to plugins/platforms/dingtalk/adapter.py; send_message now dispatches through the platform registry (tools/send_message_tool.py:1072). The implementation needs a plugin-layer port.
• In the PR, token acquisition accepts DINGTALK_CLIENT_ID (tools/send_message_tool.py:1466), but robot_code does not fall back to that value (tools/send_message_tool.py:1503-1507). Environment-only users therefore skip proactive delivery unless they set another variable. Current adapter convention defaults robot code to the resolved client ID (plugins/platforms/dingtalk/adapter.py:211).
• The PR changes only implementation files and adds no coverage for the new routing paths.

Suggested changes

• Implement the path in the bundled DingTalk plugin's standalone_sender_fn, preserve registry dispatch, and add mocked group, OTO, session-webhook, static-webhook, and environment-only credential tests.

Automated hermes-sweeper review.

[teknium1]

client_id above can come from DINGTALK_CLIENT_ID, but this fallback only considers extra["client_id"]. That makes the advertised environment-only setup skip the proactive call unless DINGTALK_ROBOT_CODE is also set. Reuse the resolved client_id here; current main's adapter defaults robot code to its resolved client ID.

[teknium1]

Current main moved DingTalk into plugins/platforms/dingtalk/adapter.py and routes send_message through its registered standalone sender. Port this lookup/delivery path to the bundled plugin rather than importing the removed gateway.platforms.dingtalk module.

[GottZ]

This was generated by AI during triage.

Summary

Fourteen PRs address or reference the DingTalk cluster: proactive delivery, outbound and inbound media, quoted replies, card throttling, session reliability, and deployment configuration. The diffs range from broad stacked or umbrella implementations (#12769, #14333–#14336, #33899) to focused slices (#12077, #17365, #17367–#17371, #40929), but the active adapter and standalone sender now live under the DingTalk plugin contract, so the reusable changes require targeted plugin-layer ports.

Related pull requests

• feat(dingtalk): add proactive message API to send_message tool #12077 related — (+678/-179) — n/a: Adds proactive group/DM delivery, shared session-webhook lookup, and static-webhook fallback, but the diff targets the retired inline adapter and its Robot Code does not inherit an environment-only client ID; despite the keep_open review, the salvage path is a tested port to the plugin sender.
• feat(dingtalk): proactive messaging, media pipeline, card throttle + quoted-reply extraction #12769 related — (+2346/-29) — n/a: Implements the broadest plugin-layer feature set—proactive and media delivery, inbound parsing, quoted replies, card throttling, and routing fixes—but also reintroduces a DingTalk-specific core route and an unrelated broken guard script; the visible CHANGES_REQUESTED review asked for conflict/template fixes, which the author reports addressing, while the later keep_open review still requires architectural re-scope.
• fix(dingtalk): adapter reliability — websockets proxy, card QPS throttle, inbound queue #14333 [closed] related — (+411/-10) — n/a: Bundles card throttling, websocket protection, inbound queuing, and configuration changes on the retired adapter path; it remains relevant as the closed source implementation superseded by fix(dingtalk): adapter reliability — websockets proxy, card QPS throttle, inbound queue (rebased) #40929.
• feat(dingtalk): quoted-reply extraction and text handling improvements #14334 related — (+741/-11) — n/a: Adds recursive quoted-reply extraction and focused payload-shape tests, but carries the preceding stack and edits the retired adapter while logging the full quote payload at INFO; its keep_open review identifies the parser and tests as salvageable for the plugin reply fields.
• feat(dingtalk): rich-media inbound pipeline — download, parse, persist #14335 related — (+1510/-13) — n/a: Adds inbound attachment download, document parsing, persistence, and dependencies, but the diff uses the retired adapter, buffers downloads without the stated bound, passes file:// URIs where local paths are expected, and does not test the media pipeline; the keep_open review rates only a focused plugin attachment flow as salvageable.
• feat(dingtalk): proactive messaging via Robot OpenAPI + send_message_tool media support #14336 related — (+2189/-41) — n/a: Extends the stack with Robot OpenAPI routing and native media delivery, directly addressing expired or absent session webhooks, but targets a removed file, conflicts with the plugin registry, and lacks proactive-routing and media-outcome tests; the maintainer-bot keep_open verdict calls for a plugin-contract port with mocked group, DM, failure, and fallback coverage.
• fix(dingtalk): add AI Card QPS token-bucket throttle #17365 related — (+42/-4) — n/a: Isolates per-card and global throttling calls, but references three undefined limiter symbols and edits the retired adapter, so its keep_open salvage path is a complete plugin implementation with concurrency, backoff, and finalize tests.
• chore(dingtalk): gateway infra — HOME_CHANNEL injection, guard script, misc config #17367 related — (+139/-3) — n/a: Bundles home-channel hydration, display names, registration identity, editor ignores, and a new supervisor, but the guard exits before restart under set -e and the configuration and registration assumptions conflict with current supported paths; its keep_open review limits salvageability to separately justified current-main changes.
• feat(dingtalk): extract quoted-reply context for agent awareness #17368 related — (+324/-1) — n/a: Isolates quoted-reply parsing with twelve unit cases, but still imports the removed adapter, bypasses live SDK conversion, and logs complete payloads at INFO; consistent with the maintainer-bot keep_open verdict, salvage it into plugin reply fields with a callback-payload regression test.
• feat(dingtalk): rich-media inbound pipeline — download, parse, persist #17369 related — (+581/-2) — n/a: Isolates inbound media download, parsing, persistence, and optional dependencies, but the visible diff lacks a required resolver and final tuple return, does not enforce bounded reads, targets the removed adapter, and adds no tests; the keep_open review supports salvaging only the raw-extension flow through shared bounded download handling.
• feat(dingtalk): proactive messaging via Robot OpenAPI #17370 related — (+815/-6) — n/a: Isolates Robot OpenAPI token, routing, payload, upload, and adapter fallback logic, but edits the retired adapter and leaves the current standalone plugin sender unchanged while carrying unwired media code; its keep_open review requires one focused plugin implementation shared by live and standalone delivery.
• feat(send_message): MEDIA tag support + DingTalk/Feishu native routing #17371 related — (+107/-19) — n/a: Adds MEDIA and bare-path extraction plus DingTalk and Feishu routing, but imports a proactive sender absent from this PR, bypasses current plugin routing, omits required local-path filtering, and has no tests; the keep_open review supports moving only the remaining DingTalk work into the plugin contract.
• feat(dingtalk): proactive messaging via Robot OpenAPI + send_message_tool media #33899 [closed] related — (+2178/-54) — n/a: Repackages the stacked proactive and media implementation but remains relevant only as a closed duplicate of feat(dingtalk): proactive messaging via Robot OpenAPI + send_message_tool media support #14336, with overlapping slices in feat(dingtalk): proactive messaging via Robot OpenAPI #17370 and feat(send_message): MEDIA tag support + DingTalk/Feishu native routing #17371.
• fix(dingtalk): adapter reliability — websockets proxy, card QPS throttle, inbound queue (rebased) #40929 related — (+409/-10) — n/a: Rebases fix(dingtalk): adapter reliability — websockets proxy, card QPS throttle, inbound queue #14333’s reliability bundle, but still edits the removed adapter, duplicates current shared session queuing, stamps throttling before a potentially failed send, and retains the broken guard; its keep_open review supports only validated plugin-layer reliability work and tests.

Duplicates

#14333 and #40929 are the same reliability bundle, with #14333 closed as superseded by #40929; #14334/#17368 cover quoted replies, #14335/#17369 cover inbound media, #14336/#17370/#17371 cover proactive and outbound-media delivery, and #17365 extracts #14333’s throttle. #12769 is the umbrella containing most of those slices, while closed #33899 is a duplicate of #14336 and #12077 overlaps the proactive-delivery portion.

Suggested consolidation

Author action: rebase onto main, or split out the part that can merge—use #12769 as the umbrella, but separate current-plugin PRs for proactive live plus standalone delivery (#12077/#14336/#17370), quoted replies (#14334/#17368), bounded inbound media (#14335/#17369), and complete card throttling (#17365/#40929), while removing the core routing and guard-script changes. This preserves the explicit keep_open and maintainer-bot salvage verdicts and does not cross #12769’s CHANGES_REQUESTED review; keep closed #14333 and #33899 closed, and close the remaining duplicate branches only after their identified plugin-layer slices and tests have been consolidated.

Cross-PR triage: Reviewed 14 pull requests and 0 issues in this complex. Each diff was read against this issue; Assessment working set: 418 kB of PR diffs, 31 kB of issue/PR text, 33 kB of discussion (42 comments), 0 verify verdicts. verdicts reflect diff content, not PR titles. Part of an automated triage batch.