@dingtalk-real-ai/dingtalk-connector 0.8.21 → 0.8.22

package/CHANGELOG.md

@@ -7,6 +7,33 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.8.22] - 2026-05-24
+
+晋升自 `0.8.22-beta.0` 的 GA 版本，与 beta.0 内容完全一致，经过 ~3 天社区验证（无回归反馈）后正式发布。
+GA promotion of `0.8.22-beta.0` after ~3 days of community validation with no regression; functionally identical to the beta.
+
+### 升级 / Upgrade
+
+```bash
+openclaw plugins install @dingtalk-real-ai/dingtalk-connector@0.8.22
+openclaw gateway restart
+```
+
+以下内容沿用自 `0.8.22-beta.0` 的改进 / Same improvements as `0.8.22-beta.0`：
+
+## [0.8.22-beta.0] - 2026-05-21
+
+> **社区验证版本** — 计划 2-3 天观察期后晋升为 `v0.8.22`。详见 [Release Notes](docs/RELEASE_NOTES_V0.8.22-beta.0.md)。
+> Community validation release — planned to promote to `v0.8.22` after a 2-3 day observation window.
+
+### 改进 / Improvements
+
+- ✨ **单聊空回复 UX 文案优化 (#599 / #601)** — 把 `✅ 任务执行完成（无文本输出）` 改为口语化的 `好的 👌 有其他问题随时找我`，避免被用户误判为报错。私聊场景下模型对 ACK 类输入选择沉默 / 只走 thinking / 仅工具调用时落到这条兜底，新文案保留"本轮已结束"的信号但去掉系统/技术味；测试改成语义契约（不绑死字符串）。群聊兜底文案与日志 hint 不变。
+  **Soften direct-chat empty-reply fallback (#599 / #601)** — Replace `✅ 任务执行完成（无文本输出）` with the conversational `好的 👌 有其他问题随时找我`. The fallback fires when models stay silent on ACK-style inputs / only emit thinking / make tool-only calls; the new copy preserves the "turn ended" signal while dropping the system flavor that misled users into thinking it was an error. Tests refactored to semantic contracts.
+
+- ✨ **dws onboarding SSH 兼容 + 版本升级 (#565 / #598)** — `DWS_NPM_PACKAGE` 从 `1.0.13` 升到 npm 最新 `1.0.30`，新装用户拿到 dws #226 修过的 `--help` 文案。onboarding 检测 SSH / 无头环境（`SSH_CLIENT` / `SSH_TTY` / `SSH_CONNECTION`）后，自动把建议命令换成 `dws auth login --device`，避免 127.0.0.1 loopback 在无浏览器服务器上挂死。跨仓根治追踪在 [dws #327](https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli/issues/327)。
+  **dws onboarding SSH compatibility + version bump (#565 / #598)** — Bump `DWS_NPM_PACKAGE` from `1.0.13` to npm latest `1.0.30` so new installs get the dws #226 docs fix. Onboarding now detects SSH / headless env (`SSH_CLIENT` / `SSH_TTY` / `SSH_CONNECTION`) and auto-suggests `dws auth login --device` to avoid 127.0.0.1 loopback hangs on browserless servers. Cross-repo root fix tracked at [dws #327](https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli/issues/327).
+
 ## [0.8.21] - 2026-05-19
 
 晋升自 `0.8.21-beta.0` 的 GA 版本，与 beta.0 内容完全一致，经过社区验证后正式发布。  

package/bin/dingtalk-connector.js

@@ -398,7 +398,7 @@ function getDwsSpawnEnv() {
 
 // ── dws CLI install ─────────────────────────────────────────────
 const DWS_INSTALL_SCRIPT_URL = 'https://raw.githubusercontent.com/DingTalk-Real-AI/dingtalk-workspace-cli/main/scripts/install.sh';
-const DWS_NPM_PACKAGE = 'dingtalk-workspace-cli@1.0.13';
+const DWS_NPM_PACKAGE = 'dingtalk-workspace-cli@1.0.30';
 
 function isDwsInstalled() {
   const mod = ['child', 'process'].join('_');
@@ -513,6 +513,23 @@ function isDwsAuthenticated() {
   }
 }
 
+// SSH/无头环境下 dws auth login 默认走 127.0.0.1 loopback 回调，
+// 本地浏览器无法访问远端 loopback，会卡住授权流程（Issue #565 / dws #226）。
+// 检测到 SSH 时引导用户加 --device 走设备流。
+function isSshSession() {
+  const env = globalThis['proc' + 'ess'].env;
+  return !!(env.SSH_CLIENT || env.SSH_TTY || env.SSH_CONNECTION);
+}
+
+function printDwsLoginHint(prefix = '    ') {
+  const ssh = isSshSession();
+  const cmd = ssh ? 'dws auth login --device' : 'dws auth login';
+  console.log(dim(`${prefix}You can also authorize manually anytime: `) + cyan(cmd) + '\n');
+  if (ssh) {
+    console.log(dim(`${prefix}(检测到 SSH / 无头环境，已切换到 --device 设备流，避免 127.0.0.1 loopback 回调在远端无浏览器时挂起)`) + '\n');
+  }
+}
+
 async function ensureDwsCli() {
   const targetVersion = getTargetDwsVersion();
 
@@ -562,7 +579,7 @@ async function ensureDwsCli() {
       console.log(dim('  ✔ dws CLI authenticated') + '\n');
     } else {
       console.log(dim('  ℹ dws CLI not yet authenticated. Authorization will be triggered when Agent uses dws features.') + '\n');
-      console.log(dim('    You can also authorize manually anytime: ') + cyan('dws auth login') + '\n');
+      printDwsLoginHint();
     }
     return;
   }
@@ -582,7 +599,7 @@ async function ensureDwsCli() {
   const freshDisplay = freshVersion ? `v${freshVersion}` : (targetVersion ? `v${targetVersion}` : '');
   console.log(green(`  ✔ dws CLI installed (${freshDisplay})`) + '\n');
   console.log(dim('  ℹ Authorization will be triggered when Agent uses dws features.') + '\n');
-  console.log(dim('    You can also authorize manually anytime: ') + cyan('dws auth login') + '\n');
+  printDwsLoginHint();
 }
 
 // ── main ───────────────────────────────────────────────────────

package/dist/entry-bundled.mjs

@@ -23,7 +23,7 @@ var entry_bundled_default = defineBundledChannelEntry({
 		exportName: "setDingtalkRuntime"
 	},
 	async registerFull(api) {
-		const { registerGatewayMethods } = await import("./gateway-methods-B0_tBGPn.mjs");
+		const { registerGatewayMethods } = await import("./gateway-methods-COXVcCFs.mjs");
 		registerGatewayMethods(api);
 	}
 });

package/dist/{gateway-methods-BNuB2wXl.mjs → gateway-methods-C3nEHxL4.mjs}

@@ -1,7 +1,7 @@
 import { a as resolveDingtalkAccount, t as listDingtalkAccountIds } from "./accounts-CF4oK_HZ.mjs";
 import { t as dingtalkHttp } from "./http-client-DFWZgO1n.mjs";
-import { i as DINGTALK_API, o as getAccessToken } from "./utils-QEvgZ2uM.mjs";
-import { c as prepareMultiBotMentions, i as sendProactive, s as buildBotMentionTable, u as finishAICard } from "./messaging-DQwrrd68.mjs";
+import { i as DINGTALK_API, o as getAccessToken } from "./utils-DgNm1Ek_.mjs";
+import { c as prepareMultiBotMentions, i as sendProactive, s as buildBotMentionTable, u as finishAICard } from "./messaging-C2zJ8O-o.mjs";
 import { c as getUnionId, d as recallEmotionReply } from "./utils-legacy-CALCPP1t.mjs";
 //#region src/docs.ts
 var DingtalkDocsClient = class {

package/dist/gateway-methods-COXVcCFs.mjs

@@ -0,0 +1,2 @@
+import { t as registerGatewayMethods } from "./gateway-methods-C3nEHxL4.mjs";
+export { registerGatewayMethods };

package/dist/index.mjs

@@ -1,5 +1,5 @@
-import { a as initDingtalkPluginConfigSchema, i as dingtalkPlugin, n as setDingtalkRuntime } from "./runtime-BphH7_vR.mjs";
-import { t as registerGatewayMethods } from "./gateway-methods-BNuB2wXl.mjs";
+import { a as initDingtalkPluginConfigSchema, i as dingtalkPlugin, n as setDingtalkRuntime } from "./runtime-BCFW2-1B.mjs";
+import { t as registerGatewayMethods } from "./gateway-methods-C3nEHxL4.mjs";
 //#region index.ts
 /**
 * 检测同一 plugin id 在多个路径被加载的情况。

package/dist/{media-BRqGsKUB.mjs → media-BViJQGgb.mjs}

@@ -1,5 +1,5 @@
 import { n as dingtalkOapiHttp, t as dingtalkHttp } from "./http-client-DFWZgO1n.mjs";
-import { a as DINGTALK_OAPI } from "./utils-QEvgZ2uM.mjs";
+import { a as DINGTALK_OAPI } from "./utils-DgNm1Ek_.mjs";
 import { createRequire } from "node:module";
 import * as fs from "fs";
 import * as path from "path";
@@ -287,7 +287,7 @@ async function extractAudioDuration(filePath, log) {
 */
 async function sendVideoMessage(config, sessionWebhook, fileName, mediaId, log, metadata) {
 	try {
-		const token = await (await import("./utils-BqUoUOwd.mjs")).getAccessToken(config);
+		const token = await (await import("./utils-TpPdfqWr.mjs")).getAccessToken(config);
 		const videoMessage = {
 			msgtype: "video",
 			video: {
@@ -315,8 +315,8 @@ async function sendVideoMessage(config, sessionWebhook, fileName, mediaId, log,
 */
 async function sendVideoProactive(config, target, videoMediaId, picMediaId, metadata, log) {
 	try {
-		const token = await (await import("./utils-BqUoUOwd.mjs")).getAccessToken(config);
-		const { DINGTALK_API } = await import("./utils-BqUoUOwd.mjs");
+		const token = await (await import("./utils-TpPdfqWr.mjs")).getAccessToken(config);
+		const { DINGTALK_API } = await import("./utils-TpPdfqWr.mjs");
 		const msgParam = {
 			duration: metadata?.duration.toString() || "60000",
 			videoMediaId,
@@ -361,8 +361,8 @@ async function sendVideoProactive(config, target, videoMediaId, picMediaId, meta
 */
 async function sendAudioProactive(config, target, fileName, mediaId, log, durationMs) {
 	try {
-		const token = await (await import("./utils-BqUoUOwd.mjs")).getAccessToken(config);
-		const { DINGTALK_API } = await import("./utils-BqUoUOwd.mjs");
+		const token = await (await import("./utils-TpPdfqWr.mjs")).getAccessToken(config);
+		const { DINGTALK_API } = await import("./utils-TpPdfqWr.mjs");
 		const msgParam = {
 			mediaId,
 			duration: durationMs && durationMs > 0 ? durationMs.toString() : "60000"
@@ -399,8 +399,8 @@ async function sendAudioProactive(config, target, fileName, mediaId, log, durati
 */
 async function sendFileProactive(config, target, fileInfo, mediaId, log) {
 	try {
-		const token = await (await import("./utils-BqUoUOwd.mjs")).getAccessToken(config);
-		const { DINGTALK_API } = await import("./utils-BqUoUOwd.mjs");
+		const token = await (await import("./utils-TpPdfqWr.mjs")).getAccessToken(config);
+		const { DINGTALK_API } = await import("./utils-TpPdfqWr.mjs");
 		const resolvedFileName = fileInfo.fileName || path.basename(fileInfo.path);
 		const msgParam = {
 			mediaId,

package/dist/{media-DD7Rlljd.mjs → media-CIO05hZn.mjs}

@@ -1,2 +1,2 @@
-import { a as processVideoMarkers, i as processRawMediaPaths, l as toLocalPath, s as sendFileProactive } from "./media-BRqGsKUB.mjs";
+import { a as processVideoMarkers, i as processRawMediaPaths, l as toLocalPath, s as sendFileProactive } from "./media-BViJQGgb.mjs";
 export { processRawMediaPaths, processVideoMarkers, sendFileProactive, toLocalPath };

package/dist/{message-handler-CPGT1bgU.mjs → message-handler-0NLKAqHU.mjs}

@@ -1,10 +1,10 @@
-import { u as uploadMediaToDingTalk } from "./media-BRqGsKUB.mjs";
+import { u as uploadMediaToDingTalk } from "./media-BViJQGgb.mjs";
 import { a as resolveDingtalkAccount } from "./accounts-CF4oK_HZ.mjs";
-import { r as CHANNEL_ID, t as getDingtalkRuntime } from "./runtime-BphH7_vR.mjs";
+import { r as CHANNEL_ID, t as getDingtalkRuntime } from "./runtime-BCFW2-1B.mjs";
 import { n as createLoggerFromConfig } from "./logger-BDWwViGT.mjs";
 import { t as dingtalkHttp } from "./http-client-DFWZgO1n.mjs";
-import { n as groupChatLacksVisibleRepliesAutomatic, r as pickEmptyReplyFallbackText, s as getOapiAccessToken, t as emptyGroupReplyLogHint } from "./utils-QEvgZ2uM.mjs";
-import { a as sendTextMessage, d as isQpsLimitError, f as streamAICard, i as sendProactive, l as createAICardForTarget, r as sendMessage, t as sendMarkdownMessage, u as finishAICard } from "./messaging-DQwrrd68.mjs";
+import { n as groupChatLacksVisibleRepliesAutomatic, r as pickEmptyReplyFallbackText, s as getOapiAccessToken, t as emptyGroupReplyLogHint } from "./utils-DgNm1Ek_.mjs";
+import { a as sendTextMessage, d as isQpsLimitError, f as streamAICard, i as sendProactive, l as createAICardForTarget, r as sendMessage, t as sendMarkdownMessage, u as finishAICard } from "./messaging-C2zJ8O-o.mjs";
 import { a as QUEUE_BUSY_ACK_PHRASES, n as normalizeSlashCommand, t as buildSessionContext } from "./session-DJ4jYqPv.mjs";
 import { d as recallEmotionReply, o as getAccessToken, r as addEmotionReply, s as getOapiAccessToken$1, t as DINGTALK_API } from "./utils-legacy-CALCPP1t.mjs";
 import "./chunk-upload-6p9cf3UB.mjs";
@@ -364,7 +364,7 @@ function createDingtalkReplyDispatcher(params) {
 				finalText = await processAudioMarkers(finalText, "", account.config, oapiToken, log, true, target);
 				finalText = await uploadAndReplaceFileMarkers(finalText, "", account.config, oapiToken, log, true, target);
 				log.info(`[DingTalk][closeStreaming] 准备调用 processRawMediaPaths`);
-				const { processRawMediaPaths } = await import("./media-DD7Rlljd.mjs");
+				const { processRawMediaPaths } = await import("./media-CIO05hZn.mjs");
 				finalText = await processRawMediaPaths(finalText, account.config, oapiToken, log, target);
 				log.info(`[DingTalk][closeStreaming] processRawMediaPaths 处理完成`);
 			} else log.warn(`[DingTalk][closeStreaming] oapiToken 为空，跳过媒体处理`);
@@ -480,7 +480,7 @@ function createDingtalkReplyDispatcher(params) {
 					const oapiToken = await getOapiAccessToken(account.config);
 					if (oapiToken) {
 						log.info(`[DingTalk][deliver] 检测到 final 响应，准备处理裸露文件路径`);
-						const { processRawMediaPaths } = await import("./media-DD7Rlljd.mjs");
+						const { processRawMediaPaths } = await import("./media-CIO05hZn.mjs");
 						text = await processRawMediaPaths(text, account.config, oapiToken, log, target);
 						log.info(`[DingTalk][deliver] 裸露文件路径处理完成`);
 					}
@@ -1751,7 +1751,7 @@ async function handleDingTalkMessageInternal(params) {
 				finalText = await processVideoMarkers(finalText, "", config, oapiToken, log, true, mediaTarget);
 				finalText = await processAudioMarkers(finalText, "", config, oapiToken, log, true, mediaTarget);
 				finalText = await uploadAndReplaceFileMarkers(finalText, "", config, oapiToken, log, true, mediaTarget);
-				const { processRawMediaPaths } = await import("./media-DD7Rlljd.mjs");
+				const { processRawMediaPaths } = await import("./media-CIO05hZn.mjs");
 				finalText = await processRawMediaPaths(finalText, config, oapiToken, log, mediaTarget);
 			}
 			let textToSend = finalText.trim();

package/dist/{messaging-DQwrrd68.mjs → messaging-C2zJ8O-o.mjs}

@@ -1,7 +1,7 @@
-import { u as uploadMediaToDingTalk } from "./media-BRqGsKUB.mjs";
+import { u as uploadMediaToDingTalk } from "./media-BViJQGgb.mjs";
 import { n as createLoggerFromConfig } from "./logger-BDWwViGT.mjs";
 import { t as dingtalkHttp } from "./http-client-DFWZgO1n.mjs";
-import { i as DINGTALK_API, o as getAccessToken, s as getOapiAccessToken } from "./utils-QEvgZ2uM.mjs";
+import { i as DINGTALK_API, o as getAccessToken, s as getOapiAccessToken } from "./utils-DgNm1Ek_.mjs";
 import { r as MEDIA_MSG_TYPES } from "./session-DJ4jYqPv.mjs";
 //#region src/services/messaging/card.ts
 const AI_CARD_TEMPLATE_ID = "02fcf2f4-5e02-4a85-b672-46d1f715543e.schema";
@@ -851,7 +851,7 @@ async function sendMediaToDingTalk(params) {
 			});
 		}
 		let resolvedMediaUrl = mediaUrl;
-		const { toLocalPath } = await import("./media-DD7Rlljd.mjs");
+		const { toLocalPath } = await import("./media-CIO05hZn.mjs");
 		const _fs = await import("fs");
 		const _path = await import("path");
 		const directPath = toLocalPath(mediaUrl);
@@ -886,7 +886,7 @@ async function sendMediaToDingTalk(params) {
 		}
 		if (mediaType === "video") {
 			const videoMarker = `[DINGTALK_VIDEO]{"path":"${mediaUrl}"}[/DINGTALK_VIDEO]`;
-			const { processVideoMarkers } = await import("./media-DD7Rlljd.mjs");
+			const { processVideoMarkers } = await import("./media-CIO05hZn.mjs");
 			await processVideoMarkers(videoMarker, "", config, oapiToken, console, true, targetParam);
 			if (text?.trim()) {
 				const result = await sendProactive(config, targetParam, text, {
@@ -910,7 +910,7 @@ async function sendMediaToDingTalk(params) {
 			fileName,
 			fileType: ext || "file"
 		};
-		const { sendFileProactive } = await import("./media-DD7Rlljd.mjs");
+		const { sendFileProactive } = await import("./media-CIO05hZn.mjs");
 		await sendFileProactive(config, targetParam, fileInfo, uploadResult.mediaId, log);
 		return {
 			ok: true,

package/dist/{runtime-BphH7_vR.mjs → runtime-BCFW2-1B.mjs}

@@ -1,9 +1,9 @@
-import { d as __exportAll } from "./media-BRqGsKUB.mjs";
+import { d as __exportAll } from "./media-BViJQGgb.mjs";
 import { a as resolveDingtalkAccount, c as addWildcardAllowFrom, d as hasConfiguredSecretInput, f as normalizeAccountId, l as createDefaultChannelRuntimeState, m as resolveDefaultGroupPolicy, o as resolveDingtalkCredentials, p as resolveAllowlistProviderRuntimeGroupPolicy, r as resolveDefaultDingtalkAccountId, s as DEFAULT_ACCOUNT_ID, t as listDingtalkAccountIds, u as formatDocsLink } from "./accounts-CF4oK_HZ.mjs";
 import { t as createLogger } from "./logger-BDWwViGT.mjs";
 import { t as dingtalkHttp } from "./http-client-DFWZgO1n.mjs";
-import "./utils-QEvgZ2uM.mjs";
-import { n as sendMediaToDingTalk, o as sendTextToDingTalk } from "./messaging-DQwrrd68.mjs";
+import "./utils-DgNm1Ek_.mjs";
+import { n as sendMediaToDingTalk, o as sendTextToDingTalk } from "./messaging-C2zJ8O-o.mjs";
 import { createRequire } from "node:module";
 import { z, z as z$1 } from "zod";
 //#region src/secret-input.ts
@@ -905,7 +905,7 @@ async function monitorDingtalkProvider(opts = {}) {
 	const log = createLogger(cfg.channels?.["dingtalk-connector"]?.debug ?? false);
 	const [accountsModule, monitorAccountModule, monitorSingleModule] = await Promise.all([
 		import("./accounts-BSIiLyZa.mjs"),
-		import("./message-handler-CPGT1bgU.mjs"),
+		import("./message-handler-0NLKAqHU.mjs"),
 		import("./connection-D4uO_J9G.mjs")
 	]);
 	const { resolveDingtalkAccount, listEnabledDingtalkAccounts } = accountsModule;

package/dist/{utils-QEvgZ2uM.mjs → utils-DgNm1Ek_.mjs}

@@ -66,7 +66,7 @@ async function getOapiAccessToken(config) {
 *
 * 背景
 * ----
-* 群聊场景下用户 @ 机器人后看到「任务执行完成（无文本输出）」，常见根因不是 connector，
+* 群聊场景下用户 @ 机器人后看到空回复兜底文案，常见根因不是 connector，
 * 而是上游 OpenClaw 的 reply delivery mode（`source-reply-delivery-mode.ts`）：群聊
 * 默认走 `message_tool_only`，会跳过 `onPartialReply` 与 `accumulatedText`，
 * 导致本插件累积的文本始终为空，最后落到 connector 的空回复兜底。
@@ -78,11 +78,13 @@ async function getOapiAccessToken(config) {
 *     }
 *   }
 *
-* 本模块的优化目标：让群聊场景看到的兜底文案变成一句可操作的提示，
-* 并在日志里给运维一份完整指引，而不是一句无信息量的「任务执行完成」。
-* 单聊场景的兜底文案保持原样（单聊空 final 通常是模型自身输出空）。
+* 本模块的优化目标：让兜底文案在两种场景下都自然不"像报错"——
+*   - 群聊：返回一段可操作的运维指引（指向 `messages.groupChat.visibleReplies`）。
+*   - 单聊：返回一段口语化的简短确认语（单聊空 final 通常是模型自身没产出文本，
+*     如纯思考、只走 tool_call、对 ACK 类输入选择沉默等），并隐含邀请用户继续提问，
+*     避免历史上的「✅ 任务执行完成（无文本输出）」让用户误以为是报错。
 */
-const DIRECT_FALLBACK_TEXT = "✅ 任务执行完成（无文本输出）";
+const DIRECT_FALLBACK_TEXT = "好的 👌 有其他问题随时找我";
 const GROUP_FALLBACK_TEXT = [
 	"ℹ️ 暂未收到模型回复内容。",
 	"若群聊频繁出现该提示，请联系机器人管理员检查 OpenClaw 配置：",

package/dist/{utils-BqUoUOwd.mjs → utils-TpPdfqWr.mjs}

@@ -1,4 +1,4 @@
 import "./logger-BDWwViGT.mjs";
-import { i as DINGTALK_API, o as getAccessToken } from "./utils-QEvgZ2uM.mjs";
+import { i as DINGTALK_API, o as getAccessToken } from "./utils-DgNm1Ek_.mjs";
 import "./session-DJ4jYqPv.mjs";
 export { DINGTALK_API, getAccessToken };

package/docs/RELEASE_NOTES_V0.8.22-beta.0.md

@@ -0,0 +1,107 @@
+# Release Notes - v0.8.22-beta.0
+
+> **社区验证版本** — 计划经过 ~2-3 天社区验证后晋升为正式版 `v0.8.22`。
+> **Community validation release** — planned to promote to GA `v0.8.22` after ~2-3 days of community validation.
+
+## 🎉 本次重点 / Highlights
+
+本版本聚焦 UX 文案与 dws onboarding 体验：
+
+1. 把单聊空回复兜底文案 `✅ 任务执行完成（无文本输出）` 换成口语化确认语 `好的 👌 有其他问题随时找我`，避免被用户误判为报错（#599）
+2. dws CLI 内置版本从 `1.0.13` 升到 npm 最新 `1.0.30`，新装用户拿到正确的 `dws auth login --help` 文案
+3. onboarding 检测 SSH / 无头环境（`SSH_CLIENT` / `SSH_TTY` / `SSH_CONNECTION`），自动建议 `dws auth login --device`，避免 127.0.0.1 loopback 在远端无浏览器服务器上挂起（#565）
+
+This release focuses on UX copy + dws onboarding experience:
+
+1. Replace direct-chat empty-reply fallback `✅ 任务执行完成（无文本输出）` with conversational confirmation `好的 👌 有其他问题随时找我`, so users no longer mistake it for an error (#599)
+2. Bump pinned dws CLI from `1.0.13` to npm latest `1.0.30`; new installs get the corrected `dws auth login --help` copy
+3. Detect SSH / headless env in onboarding and auto-suggest `dws auth login --device`, avoiding 127.0.0.1 loopback hangs on remote headless servers (#565)
+
+## ✨ 改进 / Improvements
+
+### 单聊空回复 UX 文案优化 (#599 / #601)
+
+**现象**：用户对一段说明回「知道了」后，机器人显示 `✅ 任务执行完成（无文本输出）`，被误判为报错。
+
+**根因**：私聊场景下模型可能因 ACK 类输入选择沉默（只走 thinking / tool_call、或纯输出空文本）。connector 的空回复兜底文案系统/技术味偏重，让用户以为是异常。
+
+**改动**：
+
+- `src/utils/empty-reply.ts:23` — `DIRECT_FALLBACK_TEXT` 改为 `好的 👌 有其他问题随时找我`，保留"本轮已结束"信号但去掉技术味
+- 测试改成语义契约（不绑死字符串）：不出现报错感字样 / 以「好」开头 / 包含追问引导 / 与群聊文案不同
+- 群聊兜底文案与日志 hint 维持不变（仍是面向运维的可操作指引）
+
+**Phenomenon**: After replying "知道了" (got it) to a bot's explanation, users saw `✅ 任务执行完成（无文本输出）` and mistook it for an error.
+
+**Root cause**: In direct chat, models may choose to stay silent on ACK-style input (only thinking / tool_call, or empty text output). The connector's fallback copy was too system-y, leading users to misjudge it as a fault.
+
+**Changes**:
+
+- `src/utils/empty-reply.ts:23` — `DIRECT_FALLBACK_TEXT` becomes `好的 👌 有其他问题随时找我`, keeping the "turn ended" signal while dropping the system flavor
+- Tests refactored to semantic contracts (no hardcoded strings): no error-flavored words / starts with 「好」 / contains a follow-up invitation / differs from group fallback
+- Group-chat fallback copy and log hint unchanged (still actionable ops guidance)
+
+### dws onboarding SSH 兼容 + 版本升级 (#565 / #598)
+
+**现象**：SSH / 无头服务器上首次 `dws auth login` 卡死——dws CLI 默认走 127.0.0.1 loopback 回调，本地浏览器无法访问远端 loopback。
+
+**根因**：connector pin 的 dws 是 `1.0.13`，此版本 `--help` 文案描述与实际行为相反，SSH 用户照着 help 跑必然踩坑。
+
+**改动**：
+
+- `bin/dingtalk-connector.js:401` — `DWS_NPM_PACKAGE` 从 `1.0.13` → `1.0.30`（npm latest，含上游 dws #226 文档修复）
+- 新增 `isSshSession()`：检测 `SSH_CLIENT` / `SSH_TTY` / `SSH_CONNECTION` 三个环境变量
+- 新增 `printDwsLoginHint()` 辅助：SSH 命中时把 `dws auth login` 换成 `dws auth login --device`，并附一句说明
+- 把"已安装/全新安装"两条路径的登录提示统一走 `printDwsLoginHint()`，避免分叉
+
+**根治方向（跨仓 follow-up）**：
+
+- [dws #327](https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli/issues/327) — 建议 dws 自身检测 SSH 环境自动降级到 `--device`，根治后 connector 这边的兜底逻辑可以择机删除
+- 「对话框内授权」是更大的跨仓 UX 改造，需要 dws 支持非 CLI 流程或 Web flow，本版本不涉及
+
+**Phenomenon**: First-time `dws auth login` hangs on SSH / headless servers — the dws CLI defaults to a 127.0.0.1 loopback callback that the local browser can't reach.
+
+**Root cause**: connector pinned dws `1.0.13` whose `--help` text described the opposite of actual behavior; SSH users following the help inevitably hit the trap.
+
+**Changes**:
+
+- `bin/dingtalk-connector.js:401` — `DWS_NPM_PACKAGE` from `1.0.13` → `1.0.30` (npm latest, including upstream dws #226 docs fix)
+- Add `isSshSession()`: detects `SSH_CLIENT` / `SSH_TTY` / `SSH_CONNECTION` env vars
+- Add `printDwsLoginHint()` helper: when SSH is detected, suggest `dws auth login --device` with a brief reason
+- Unify login hint between "already installed" and "fresh install" branches via `printDwsLoginHint()` to avoid drift
+
+**Long-term root fix (cross-repo follow-up)**:
+
+- [dws #327](https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli/issues/327) — propose dws itself detect SSH and auto-fall back to `--device`. Once that lands, the connector-side workaround can be removed.
+- "In-chat authorization" is a larger cross-repo UX overhaul (needs dws to support non-CLI / Web flow); not in scope for this release.
+
+## 🧪 验证 / Validation
+
+- `tests/empty-reply.unit.test.ts` — 9/9 单测通过（语义契约风格）
+- `node --check bin/dingtalk-connector.js` — 语法通过
+- 手动验证：设置 `SSH_CLIENT` 环境变量后，onboarding 提示自动切到 `dws auth login --device`
+
+## 📦 升级方式 / How to upgrade
+
+```bash
+openclaw plugins install @dingtalk-real-ai/dingtalk-connector@0.8.22-beta.0
+openclaw gateway restart
+```
+
+或者：
+
+```bash
+npm install -g @dingtalk-real-ai/dingtalk-connector@0.8.22-beta.0
+```
+
+## ⏭️ 后续节奏 / Next steps
+
+- **2026-05-22 ~ 2026-05-24**：社区使用反馈窗口，2-3 天观察期
+- **～2026-05-24 之后**：若无回归，晋升为正式版 `v0.8.22`
+- 升级遇到问题请提交到 [Issues](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues)，按置顶 [#584](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/584) / [#585](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/585) 的模板补全反馈信息
+
+## 🔗 关联 / References
+
+- Issue [#599](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/599) → PR [#601](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/pull/601)
+- Issue [#565](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/565) → PR [#598](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/pull/598)
+- 跨仓 follow-up: [dws #327](https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli/issues/327)

package/docs/RELEASE_NOTES_V0.8.22.md

@@ -0,0 +1,95 @@
+# Release Notes - v0.8.22
+
+> **GA 正式版** — 晋升自 `0.8.22-beta.0`，经 ~3 天社区验证（无回归反馈）后正式发布。
+> **General Availability** — Promoted from `0.8.22-beta.0` after ~3 days of community validation with no regression.
+
+## 🎉 本次重点 / Highlights
+
+本版本聚焦 UX 文案与 dws onboarding 体验，与 `0.8.22-beta.0` 功能完全一致：
+
+1. 把单聊空回复兜底文案 `✅ 任务执行完成（无文本输出）` 换成口语化的 `好的 👌 有其他问题随时找我`，避免被用户误判为报错（[#599](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/599) / [PR #601](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/pull/601)）
+2. 内置 dws CLI 从 `1.0.13` 升到 npm 最新 `1.0.30`，新装用户拿到正确的 `dws auth login --help` 文案
+3. onboarding 检测 SSH / 无头环境（`SSH_CLIENT` / `SSH_TTY` / `SSH_CONNECTION`），自动建议 `dws auth login --device`，避免 127.0.0.1 loopback 在远端无浏览器服务器上挂起（[#565](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/565) / [PR #598](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/pull/598)）
+
+This release focuses on UX copy + dws onboarding experience. Functionally identical to `0.8.22-beta.0`:
+
+1. Replace direct-chat empty-reply fallback `✅ 任务执行完成（无文本输出）` with conversational `好的 👌 有其他问题随时找我`, so users no longer mistake it for an error (#599 / PR #601)
+2. Bump bundled dws CLI from `1.0.13` to npm latest `1.0.30`; new installs get the corrected `dws auth login --help` copy
+3. Detect SSH / headless env in onboarding and auto-suggest `dws auth login --device`, avoiding 127.0.0.1 loopback hangs on remote headless servers (#565 / PR #598)
+
+## ✨ 改进 / Improvements
+
+### 单聊空回复 UX 文案优化 ([#599](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/599) / [PR #601](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/pull/601))
+
+**现象**：用户对一段说明回「知道了」后，机器人显示 `✅ 任务执行完成（无文本输出）`，被误判为报错。
+
+**根因**：私聊场景下模型可能因 ACK 类输入选择沉默（只走 thinking / tool_call、或纯输出空文本）。connector 的空回复兜底文案系统/技术味偏重。
+
+**改动**：
+
+- `src/utils/empty-reply.ts:23` — `DIRECT_FALLBACK_TEXT` 改为 `好的 👌 有其他问题随时找我`，保留"本轮已结束"信号但去掉技术味
+- 测试改成语义契约（不绑死字符串）：不出现报错感字样 / 以「好」开头 / 包含追问引导 / 与群聊文案不同
+- 群聊兜底文案与日志 hint 维持不变（仍是面向运维的可操作指引）
+
+### dws onboarding SSH 兼容 + 版本升级 ([#565](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/565) / [PR #598](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/pull/598))
+
+**现象**：SSH / 无头服务器上首次 `dws auth login` 卡死——dws CLI 默认走 127.0.0.1 loopback 回调，本地浏览器无法访问远端 loopback。
+
+**根因**：connector pin 的 dws 是 `1.0.13`，此版本 `--help` 文案描述与实际行为相反，SSH 用户照着 help 跑必然踩坑。
+
+**改动**：
+
+- `bin/dingtalk-connector.js:401` — `DWS_NPM_PACKAGE` 从 `1.0.13` → `1.0.30`（npm latest，含上游 dws #226 文档修复）
+- 新增 `isSshSession()`：检测 `SSH_CLIENT` / `SSH_TTY` / `SSH_CONNECTION` 三个环境变量
+- 新增 `printDwsLoginHint()` 辅助：SSH 命中时把 `dws auth login` 换成 `dws auth login --device`，并附一句说明
+- 把"已安装/全新安装"两条路径的登录提示统一走 `printDwsLoginHint()`，避免分叉
+
+**根治方向（跨仓 follow-up）**：
+
+- [dws #327](https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli/issues/327) — 建议 dws 自身检测 SSH 环境自动降级到 `--device`，根治后 connector 这边的兜底逻辑可以择机删除
+- 「对话框内授权」是更大的跨仓 UX 改造，需要 dws 支持非 CLI 流程或 Web flow，本版本不涉及
+
+## 🔒 兼容性 / Compatibility
+
+- **API 无变化**、配置 schema 无变化、导出符号无变化
+- 现有用户升级无需任何配置改动
+- 群聊行为完全不变（空回复兜底文案与日志 hint 未动）
+- 仅以下两类用户感知到差异：
+  - 私聊场景看到空回复兜底文案的用户 —— 文案更友好
+  - 全新安装 / 在 SSH 环境首次 `dws auth login` 的用户 —— 自动得到正确命令建议
+
+## 🧪 验证 / Verification
+
+**Beta 社区验证（2026-05-21 ~ 2026-05-24，~3 天）**：
+- npm `beta` tag 上 `0.8.22-beta.0` 稳定可用
+- 无任何针对私聊空回复文案 / dws SSH onboarding 的回归 issue
+
+**已验证组合 / Verified combo**：
+- OpenClaw Gateway `2026.5.12` (f066dd2)
+- Connector `0.8.22-beta.0`（已晋升为 `0.8.22`）
+- 平台 macOS（darwin 23.2.0）
+
+## 📥 安装升级 / Installation & Upgrade
+
+```bash
+openclaw plugins install @dingtalk-real-ai/dingtalk-connector@0.8.22
+openclaw gateway restart
+```
+
+或：
+
+```bash
+npm install @dingtalk-real-ai/dingtalk-connector@latest
+```
+
+## 🔗 相关链接 / Related Links
+
+- [完整变更日志 / Full Changelog](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/blob/main/CHANGELOG.md)
+- [Beta release notes (`v0.8.22-beta.0`)](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/blob/main/docs/RELEASE_NOTES_V0.8.22-beta.0.md)
+- 关联 PRs / issues：[#599](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/599) / [#601](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/pull/601) / [#565](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/issues/565) / [#598](https://github.com/DingTalk-Real-AI/dingtalk-openclaw-connector/pull/598) / [dws #327](https://github.com/DingTalk-Real-AI/dingtalk-workspace-cli/issues/327)
+
+---
+
+**发布日期 / Release Date**：2026-05-24
+**版本号 / Version**：v0.8.22
+**兼容性 / Compatibility**：OpenClaw Gateway 2026.5.7+

package/openclaw.plugin.json

@@ -1,7 +1,7 @@
 {
   "id": "dingtalk-connector",
   "name": "DingTalk Channel",
-  "version": "0.8.21",
+  "version": "0.8.22",
   "description": "Official OpenClaw DingTalk channel plugin | 钉钉官方 OpenClaw 插件",
   "author": "DingTalk Real Team",
   "main": "index.ts",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dingtalk-real-ai/dingtalk-connector",
-  "version": "0.8.21",
+  "version": "0.8.22",
   "description": "Official OpenClaw DingTalk channel plugin | 钉钉官方 OpenClaw 插件",
   "type": "module",
   "exports": {

package/src/core/message-handler.ts

@@ -1579,7 +1579,8 @@ export async function handleDingTalkMessageInternal(params: HandleMessageParams)
 
         // ✅ 异步模式下 final 文本为空时的兜底
         // 群聊场景下，常见根因是 OpenClaw `messages.groupChat.visibleReplies` 未设为 "automatic"
-        // （详见 src/utils/empty-reply.ts），给运维一份可操作的指引而不是无信息量的「任务执行完成」。
+        // （详见 src/utils/empty-reply.ts），给运维一份可操作的指引；
+        // 单聊则用口语化确认语兜底，避免被用户误判为报错。
         let textToSend = finalText.trim();
         if (!textToSend) {
           const isGroup = !isDirect;

package/src/reply-dispatcher.ts

@@ -308,8 +308,9 @@ export function createDingtalkReplyDispatcher(params: CreateDingtalkReplyDispatc
       // ✅ 如果累积的文本为空，使用默认提示文案
       // 群聊场景下，常见根因是 OpenClaw `messages.groupChat.visibleReplies` 未设为
       // "automatic"（上游 source-reply-delivery-mode.ts 走 message_tool_only 时
-      // 会跳过 onPartialReply，accumulatedText 始终为空）。给运维一份可操作的指引，
-      // 而不是一句无信息量的「任务执行完成」。详见 src/utils/empty-reply.ts。
+      // 会跳过 onPartialReply，accumulatedText 始终为空）。给运维一份可操作的指引；
+      // 单聊则用口语化确认语兜底，避免「任务执行完成（无文本输出）」让用户误判为报错。
+      // 详见 src/utils/empty-reply.ts。
       if (!finalText.trim()) {
         const isGroup = !isDirect;
         finalText = pickEmptyReplyFallbackText(isGroup);

package/src/utils/empty-reply.ts

@@ -3,7 +3,7 @@
  *
  * 背景
  * ----
- * 群聊场景下用户 @ 机器人后看到「任务执行完成（无文本输出）」，常见根因不是 connector，
+ * 群聊场景下用户 @ 机器人后看到空回复兜底文案，常见根因不是 connector，
  * 而是上游 OpenClaw 的 reply delivery mode（`source-reply-delivery-mode.ts`）：群聊
  * 默认走 `message_tool_only`，会跳过 `onPartialReply` 与 `accumulatedText`，
  * 导致本插件累积的文本始终为空，最后落到 connector 的空回复兜底。
@@ -15,12 +15,14 @@
  *     }
  *   }
  *
- * 本模块的优化目标：让群聊场景看到的兜底文案变成一句可操作的提示，
- * 并在日志里给运维一份完整指引，而不是一句无信息量的「任务执行完成」。
- * 单聊场景的兜底文案保持原样（单聊空 final 通常是模型自身输出空）。
+ * 本模块的优化目标：让兜底文案在两种场景下都自然不"像报错"——
+ *   - 群聊：返回一段可操作的运维指引（指向 `messages.groupChat.visibleReplies`）。
+ *   - 单聊：返回一段口语化的简短确认语（单聊空 final 通常是模型自身没产出文本，
+ *     如纯思考、只走 tool_call、对 ACK 类输入选择沉默等），并隐含邀请用户继续提问，
+ *     避免历史上的「✅ 任务执行完成（无文本输出）」让用户误以为是报错。
  */
 
-const DIRECT_FALLBACK_TEXT = '✅ 任务执行完成（无文本输出）';
+const DIRECT_FALLBACK_TEXT = '好的 👌 有其他问题随时找我';
 
 const GROUP_FALLBACK_TEXT = [
   'ℹ️ 暂未收到模型回复内容。',

package/dist/gateway-methods-B0_tBGPn.mjs

@@ -1,2 +0,0 @@
-import { t as registerGatewayMethods } from "./gateway-methods-BNuB2wXl.mjs";
-export { registerGatewayMethods };