@michengai/dsh-im-connect 1.0.17 → 1.0.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (54) hide show
  1. package/CHANGELOG.md +15 -0
  2. package/CHANGELOG.zh-CN.md +15 -0
  3. package/README.md +19 -2
  4. package/README.zh-CN.md +19 -2
  5. package/assets/icon.svg +27 -0
  6. package/client.js +300 -8
  7. package/lib/channels/meta.d.ts +7 -0
  8. package/lib/channels/meta.d.ts.map +1 -1
  9. package/lib/channels/meta.js +11 -0
  10. package/lib/channels/meta.js.map +1 -1
  11. package/lib/client.js +300 -8
  12. package/lib/engine/command-messages.d.ts +2 -0
  13. package/lib/engine/command-messages.d.ts.map +1 -1
  14. package/lib/engine/command-messages.js +2 -0
  15. package/lib/engine/command-messages.js.map +1 -1
  16. package/lib/engine/gateway.d.ts +16 -0
  17. package/lib/engine/gateway.d.ts.map +1 -1
  18. package/lib/engine/gateway.js +97 -4
  19. package/lib/engine/gateway.js.map +1 -1
  20. package/lib/engine/message-progress.d.ts +1 -0
  21. package/lib/engine/message-progress.d.ts.map +1 -1
  22. package/lib/engine/message-progress.js +5 -3
  23. package/lib/engine/message-progress.js.map +1 -1
  24. package/lib/engine/router.js +1 -1
  25. package/lib/engine/router.js.map +1 -1
  26. package/lib/engine/segments.d.ts +20 -0
  27. package/lib/engine/segments.d.ts.map +1 -0
  28. package/lib/engine/segments.js +80 -0
  29. package/lib/engine/segments.js.map +1 -0
  30. package/lib/engine/session-id.d.ts +11 -3
  31. package/lib/engine/session-id.d.ts.map +1 -1
  32. package/lib/engine/session-id.js +16 -10
  33. package/lib/engine/session-id.js.map +1 -1
  34. package/lib/engine/types.d.ts +8 -0
  35. package/lib/engine/types.d.ts.map +1 -1
  36. package/lib/index.d.ts +9 -1
  37. package/lib/index.d.ts.map +1 -1
  38. package/lib/index.js +41 -1
  39. package/lib/index.js.map +1 -1
  40. package/lib/manager.d.ts +17 -0
  41. package/lib/manager.d.ts.map +1 -1
  42. package/lib/manager.js +79 -3
  43. package/lib/manager.js.map +1 -1
  44. package/package.json +3 -2
  45. package/src/channels/meta.ts +16 -0
  46. package/src/engine/command-messages.ts +3 -0
  47. package/src/engine/gateway.ts +95 -4
  48. package/src/engine/message-progress.ts +6 -4
  49. package/src/engine/router.ts +1 -1
  50. package/src/engine/segments.ts +85 -0
  51. package/src/engine/session-id.ts +17 -11
  52. package/src/engine/types.ts +8 -0
  53. package/src/index.ts +55 -0
  54. package/src/manager.ts +92 -4
package/CHANGELOG.md CHANGED
@@ -1,5 +1,20 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.0.19 - 2026-10-27
4
+
5
+ - Add segmented replies: when set to "Send in segments" in an account's settings, the assistant splits one reply into several short messages at a line-exclusive separator (default `<<<MSG>>>`) and sends them sequentially; defaults to "Send as whole", preserving original behavior (#49).
6
+ - Send-gap interval control: each message, including the first, waits a random gap drawn from the minimum/maximum range configured for that account (0–60 seconds), rejecting saves where the maximum is lower than the minimum; the first segment uses stream finish, subsequent segments are sent sequentially, and any failure halts further delivery without resending the entire reply.
7
+ - Code block isolation and channel gating: separators inside fenced code blocks never split a reply, keeping code examples intact; currently enabled for QQ only (with support for account ID resolution), while unverified channels display no option, inject no system prompt, and never split.
8
+ - Segmented reply UI polish: refactor the control into a standard Select dropdown aligned side-by-side with Send mode; move long description copy into a native Tooltip hover icon (`ⓘ`) beside the label, eliminating awkward full-width notes and obsolete preset helper text.
9
+ - Add task tree session filter switch: introduce a `taskTreeSessions` switch in the plugin bundle configuration page (`plugins.bundle.config`), defaulting to off, which dynamically filters and hides messaging sessions from the official workspace task tree via `NativeTabRegistry.sessionFilters` while preserving them in the sidebar Channels tab.
10
+ - Unify IM session ID format: normalize newly created channel sessions to `dsh-im-session-<uuid>`, aligning with cross-plugin namespaces while preserving seamless backward compatibility for existing `im:` prefixed session records.
11
+
12
+ ## 1.0.18 - 2026-10-26
13
+
14
+ - Distinguish `max-tokens` turn truncation from user cancellation: when a turn ends due to output token limits (`reason.kind === 'max-tokens'`), notify the user that the maximum output length was reached and prompt them to send "continue" to proceed, instead of incorrectly reporting that the turn was stopped (#48).
15
+ - Harmonize original message status reaction for truncated turns: map message progress status to `ended` (Done `✅`) rather than `cancelled` (`🚫`) when output tokens are exhausted without delivery failure, resolving visual contradictions between the status emoji and the turn completion notice.
16
+ - Preserve backward-compatible fallback: manual stops, aborted turns, and older host versions smoothly fall back to the standard cancellation copy.
17
+
3
18
  ## 1.0.17 - 2026-10-24
4
19
 
5
20
  - Upgrade host admission policy: Declare `engines.dsh: ">=0.2.0-rc.1 <0.3.0-0"` to support the entire DeepSeek Harness `0.2.x` line (including `0.2.0-rc.1` onwards, future alphas, RCs, and stable releases) without requiring routine plugin version bumps.
@@ -4,6 +4,21 @@
4
4
 
5
5
  以下记录近期发布的版本。Git 标签与 GitHub Release 现已和这些条目同步;历史条目继续保留原始发布提交链接。
6
6
 
7
+ ## 1.0.19 - 2026-10-27
8
+
9
+ - 新增分段回复支持:账号「设置」中将「分段回复」选为「分段发送」后,助手按独占一行的分隔标记(默认 `<<<MSG>>>`)把一次回复拆成多条短消息逐条发送;默认保持「完整发送」,行为与以前一致(#49)。
10
+ - 发送间隔与节奏控制:每条消息(包括第一条)从账号设置填写的最小/最大间隔(0–60 秒)中随机取一个间隔,上限低于下限时拒绝保存;第一条沿用流式收口,后续分段逐条补发,中途失败立即停止且不整条重发。
11
+ - 代码块隔离与渠道准入:围栏代码块内部的标记不触发分段,保证代码示例完整性;当前仅在 QQ 渠道开放(支持账号实例 ID 形式识别),未开放渠道不展示选项、不注入提示词且不切分。
12
+ - 分段回复界面体验优化:重构为与面板整体一致的标准 Select 下拉框并与「发送方式」同行并排展示;说明文字收敛至标题旁原生 Tooltip 悬浮图标(`ⓘ`),消除多余跨列通栏文案与历史遗留提示。
13
+ - 新增任务树 IM 会话过滤开关:在插件详情页(`plugins.bundle.config`)新增「在任务树显示 IM 会话 (`taskTreeSessions`)」开关,默认关闭,通过 `NativeTabRegistry.sessionFilters` 在官方主工作区任务树中隐藏渠道会话;侧栏「频道」页签依然完整保留全部会话管理。
14
+ - 统一会话 ID 格式:新建 IM 会话升级为 `dsh-im-session-<uuid>` 格式,跨插件命名空间对齐,并保持对历史存量 `im:` 前缀会话的完全向下兼容。
15
+
16
+ ## 1.0.18 - 2026-10-26
17
+
18
+ - 区分输出长度截断与主动停止:当模型输出因超出 token 上限截断(`reason.kind === 'max-tokens'`)时,向用户明确提示「本次处理已达到输出长度上限,已返回的内容保留。可发送「继续」接续生成」,不再误报为人工停止(#48)。
19
+ - 协同原消息状态表情:当回合因达到 token 上限结束且无投递失败时,原消息状态标记为 `ended`(`✅已结束`)而非 `cancelled`(`🚫已取消`),消除头部状态标记与正文提示词的语义冲突。
20
+ - 保持平滑向下兼容:人工叫停、异常中断及未携带该原因的旧版宿主均自动回退至常规停止提示。
21
+
7
22
  ## 1.0.17 - 2026-10-24
8
23
 
9
24
  - 宿主准入机制全面升级:声明 `engines.dsh: ">=0.2.0-rc.1 <0.3.0-0"`,全面开放对 DeepSeek Harness 整个 `0.2.x` 系列的支持(包含已支持的 `0.2.0-rc.1` 起及后续全部 alpha/rc/正式版),非破坏性宿主升级无需再重复发版。
package/README.md CHANGED
@@ -239,7 +239,7 @@ The configuration output should contain `im-connect`. Restart DSH Web and hard-r
239
239
  The plugin follows standard DSH bundle configuration conventions. Options are located at:
240
240
  > **Sidebar → Plugins → Click `@michengai/dsh-im-connect`** (the host's `plugins.bundle.config` slot).
241
241
 
242
- Two native switches are available. Their values are persisted in `channels.json` under the plugin's `stateDir` and survive restarts; they are not two equivalent Cordis YAML options. `sidebarEntry` is managed through this UI, while `onlineUpdate` is also subject to the host lock described below:
242
+ Three native switches are available. Their values are persisted in `channels.json` under the plugin's `stateDir` and survive restarts; they are not equivalent Cordis YAML options. `sidebarEntry` and `taskTreeSessions` are managed through this UI, while `onlineUpdate` is also subject to the host lock described below:
243
243
 
244
244
  ### 1. Sidebar Entry (`sidebarEntry`)
245
245
  - **Default**: Disabled (`false`)
@@ -262,6 +262,14 @@ Two native switches are available. Their values are persisted in `channels.json`
262
262
  Once configured, the updater is disabled at startup, the update action stays hidden, and the online-update switch is disabled. The host lock takes precedence over the user's choice in `channels.json` and cannot be lifted through the UI. Removing the host lock restores the saved user preference.
263
263
  - **Update Modes**: When a newer release is available, **Update automatically** runs only when the DSH CLI or Desktop update service is available; otherwise, the dialog provides a profile-specific manual command to copy and run.
264
264
 
265
+ ### 3. Show IM Sessions in Task Tree (`taskTreeSessions`)
266
+ - **Default**: Disabled (`false`, hides IM sessions in the workspace task tree by default to keep daily workspaces clean)
267
+ - **Description**: Controls whether messaging channel sessions appear in the official workspace task tree.
268
+ - **Effect**:
269
+ - **Workspace Decluttering**: When disabled, all messaging sessions (including `dsh-im-session-*`, legacy `im:*` prefixes, and active channel session bindings) are automatically filtered out from the official workspace task tree, preventing high-frequency chats from flooding your daily development workspaces;
270
+ - **Channels Tab Preserved**: Filtering applies only to the official workspace tree. All channel sessions remain fully available and accessible at any time under the sidebar's **Channels** tab;
271
+ - **Lightweight Pipeline Collaboration**: Implemented via the `NativeTabRegistry.sessionFilters` inter-plugin protocol without invasive host hijacking. Toggling takes effect immediately and interoperates smoothly with Automation and Archive Manager. Non-supporting host shells degrade gracefully with a one-time warning.
272
+
265
273
  ## Usage
266
274
 
267
275
  Open **Settings → IM Assistant**, select **Add account** under the target channel, then choose that account's workspace, model, permission, private-access mode, and send mode. To register a new workspace, click **Add workspace…** in the dropdown footer to invoke the system folder picker (manual path inputs are disallowed); hosts lacking native folder pickers show "This Host cannot create workspaces" (upgrade to one of the supported host releases listed in Requirements, or add via the host sidebar).
@@ -280,6 +288,7 @@ Open **Settings → IM Assistant**, select **Add account** under the target chan
280
288
  | Sessions / workspaces | `/sessions`, `/session <number or ID>`; `/workspaces`, `/workspace <number or ID>` | Resume ordinary Chat sessions; workspace selection creates a session without changing account defaults |
281
289
  | Task controls | `/stop`, `/steer <text>`, `/queue` | Stop, provide instructions, or inspect the queue; stopping preserves Host queued messages |
282
290
  | Send mode | Open Settings on the account row and choose Queue or Steer under **Send mode** | Queue (the default) keeps today's behavior; Steer hands an ordinary message to the running task as additional instructions immediately (same as `/steer`), and behaves like Queue while the task is idle |
291
+ | Segmented replies | Open Settings on the account row, choose Send in segments under **Segmented replies**, and fill in the send-gap range | Defaults to Send as whole; when set to Send in segments, the assistant splits one reply into several short messages at the separator, and the first message also waits a random gap. See [Segmented replies](#segmented-replies) |
283
292
  | Session with a preset | `/presets`, `/preset <number or ID>`, `/preset --default` | Starts and connects a new session in the current workspace without changing account defaults |
284
293
  | Model / reasoning | `/models`, `/model <number or provider/model>`, `/reasoning [effort or --default]` | Changes the current selection and updates the Host default for subsequent Chat sessions |
285
294
  | Result recovery | `/delivery`, `/delivery retry <record-ID>` | Check recent deliveries and resend text from the original task |
@@ -305,6 +314,14 @@ Telegram topics are automatically named once from the first non-fallback session
305
314
  - The plugin configuration `topicNaming` accepts `once` (default), `follow` (follow valid titles), or `off` (disable automatic naming). `/topicname on` does not override global `off`. Explicit `/rename` remains available regardless of automatic naming settings.
306
315
  - A manual rename event in a group forum locks automatic naming. Private topics cannot rely on that event for manual rename detection; use `/topicname off`. Naming and lock state persist across restarts in `topic-titles.json` under the state directory.
307
316
 
317
+ ### Segmented replies
318
+
319
+ When **Segmented replies** is set to Send in segments for an account, the assistant splits one reply at a separator and sends the pieces one by one, which reads like a few messages in a row. It defaults to Send as whole and behavior is unchanged while off. It is currently enabled for QQ only (verified end to end); other channels do not show the option and never split.
320
+
321
+ - **Send gap**: fill in the minimum and maximum gap (seconds, 0–60). Every message, including the first, waits a random gap drawn from that range; saving is rejected when the maximum is lower than the minimum, and changes apply immediately.
322
+ - **Separator**: set by the plugin configuration `segmentMarker`, default `<<<MSG>>>`, and must occupy its own line. The same text inside a fenced code block never splits a reply, so code samples stay intact.
323
+ - **Where it is stored**: the toggle and range live per account in `channels.json`; the plugin configuration `segmentReply` acts as the default for every account, with the account setting taking precedence. If one segment fails to send, the rest stop instead of resending the whole reply, so no duplicate messages.
324
+
308
325
  ### Connecting Slack
309
326
 
310
327
  Slack uses a Socket Mode long connection, so no public URL or request URL is required:
@@ -343,7 +360,7 @@ Command permission does not grant DM admission or replace tool approval. Enabled
343
360
  | Access | Groups need no binding, only a mention. Each account can allow only approved users or all DM users; approved-only is the default, and WeChat / Feishu / Lark / QQ QR scanners are added to that account's allowlist automatically |
344
361
  | Management API | Uses `/api/dsh-im-connect`, following the REST prefix used by other DSH plugins. It delegates Host, Origin, and Cookie checks to Host `connection.requestRejection`, including local requests. Unavailable authentication returns 503; mutations retain JSON, client-header, and 1 MiB limits |
345
362
  | Secrets | WeChat tokens and other secrets prefer DSH `ctx.credentials`; otherwise they use plaintext `%DSH_HOME%\dsh-im-connect\secrets.json`, restricted to the current user and never safe to sync or share |
346
- | Account state | `channels.json` stores per-account workspace, model, permission, private access, send mode, enablement, and credential refs, not raw secrets |
363
+ | Account state | `channels.json` stores per-account workspace, model, permission, private access, send mode, segmented-reply toggle and gaps, enablement, and credential refs, not raw secrets |
347
364
  | Browser payloads | Never include tokens, secrets, App Secrets, or internal error details |
348
365
  | WeChat protocol | Official iLink only; no reverse-engineered personal WeChat protocol |
349
366
  | Tool approval | The task initiator replies in the chat bound to that session. DM admission decides who can chat and no longer gates approvals, and approvals never go back to the web. No reply within 5 minutes cancels the action instead of queueing later text |
package/README.zh-CN.md CHANGED
@@ -239,7 +239,7 @@ dsh --profile web --dump-config
239
239
  插件遵循 DSH 官方扩展配置规范,配置项位于:
240
240
  > **主界面侧边栏「插件」→ 点击 `@michengai/dsh-im-connect` 详情页**(对应宿主 `plugins.bundle.config` 槽位)。
241
241
 
242
- 此处提供两个原生扁平行开关。界面开关值保存在插件 `stateDir` 下的 `channels.json` 中,重启后保留;它们不是两个等价的 Cordis YAML 配置项。`sidebarEntry` 只通过此界面管理,`onlineUpdate` 另受下述宿主锁定规则约束:
242
+ 此处提供三个原生扁平行开关。界面开关值保存在插件 `stateDir` 下的 `channels.json` 中,重启后保留;它们不是等价的 Cordis YAML 配置项。`sidebarEntry` 和 `taskTreeSessions` 只通过此界面管理,`onlineUpdate` 另受下述宿主锁定规则约束:
243
243
 
244
244
  ### 1. 侧边栏入口 (`sidebarEntry`)
245
245
  - **默认状态**:关闭(`false`)
@@ -262,6 +262,14 @@ dsh --profile web --dump-config
262
262
  配置生效后,更新器在启动时即被禁用,更新入口隐藏,详情页在线更新开关置灰。宿主锁定优先于 `channels.json` 中的用户选择,界面不能解除锁定;宿主移除锁定后,重新按已保存的用户选择生效。
263
263
  - **更新模式**:发现新版后,只有检测到 DSH CLI 或 Desktop 更新服务时才可使用“自动更新”;其他环境会在弹窗中提供可复制、与当前 Profile 对应的手工更新命令。
264
264
 
265
+ ### 3. 在任务树显示 IM 会话 (`taskTreeSessions`)
266
+ - **默认状态**:关闭(`false`,默认在任务树隐藏即时通讯会话,保持日常工作区清爽)
267
+ - **功能说明**:控制是否在官方工作区任务树中显示各渠道产生的即时通讯会话。
268
+ - **生效效果**:
269
+ - **降噪隔离**:关闭后,各渠道产生的即时通讯会话(包括新格式 `dsh-im-session-*`、存量 `im:*` 前缀以及活跃频道绑定会话)自动从左侧官方工作区树中过滤,避免高频沟通的即时会话刷满日常开发工作区;
270
+ - **频道面板不受影响**:关闭仅作用于主任务树,在侧栏「频道」页签中依然完整保留并可随时点开、回复和复盘全部渠道会话;
271
+ - **轻量管道协同**:基于 `NativeTabRegistry.sessionFilters` 标准协作协议实现,无需深度劫持宿主组件,切换即时生效,与定时插件及归档管理等第三方插件完全兼容。未支持该协议的外壳会自动安全降级并提示。
272
+
265
273
  ## 使用
266
274
 
267
275
  打开「设置 → IM助理」,在目标渠道点击「添加账号」,并为该账号选择工作区、模型、权限、私聊准入和发送方式。若需要新工作区,可展开工作区下拉列表点击底部的「添加工作区…」直接调起系统文件选择器(禁止手输路径);不支持原生目录选择器的宿主会提示「当前 Host 无法新增工作区」,请升级到「环境要求」中列出的受支持宿主版本,或直接在宿主侧栏添加工作区。
@@ -280,6 +288,7 @@ dsh --profile web --dump-config
280
288
  | 会话 / 工作区 | `/sessions`、`/session <序号或ID>`;`/workspaces`、`/workspace <序号或ID>` | 可接续普通 Chat 会话;选择工作区会新建会话,不修改账号默认配置 |
281
289
  | 任务控制 | `/stop`、`/steer <内容>`、`/queue` | 停止、补充指令、查看队列;停止保留 Host 排队消息 |
282
290
  | 发送方式 | 点击账号右侧「设置」,在「发送方式」选择排队发送或插话发送 | 默认排队发送,行为不变;插话发送把普通消息作为补充指令立即交给运行中的任务(等同 `/steer`),任务空闲时与排队发送相同 |
291
+ | 分段回复 | 点击账号右侧「设置」,在「分段回复」选择「分段发送」并填写发送间隔区间 | 默认完整发送;选择分段发送后助手用分隔标记把一次回复拆成多条短消息,第一条也等随机间隔,规则见[分段回复](#分段回复) |
283
292
  | 预设新会话 | `/presets`、`/preset <序号或ID>`、`/preset --default` | 使用指定预设在当前工作区新建并接续,不改变账号默认 |
284
293
  | 模型 / 推理 | `/models`、`/model <序号或provider/model>`、`/reasoning [等级或 --default]` | 修改当前选择,并更新宿主后续 Chat 新会话的默认选择 |
285
294
  | 结果补发 | `/delivery`、`/delivery retry <记录ID>` | 查看近期交付状态,按记录补发原任务文字结果 |
@@ -299,6 +308,14 @@ Telegram 话题默认使用第一条非兜底会话标题自动命名一次,
299
308
  - 插件配置 `topicNaming` 支持 `once`(默认)、`follow`(跟随有效标题)和 `off`(关闭自动命名);`/topicname on` 不会覆盖全局 `off`。显式 `/rename` 不受自动命名开关限制。
300
309
  - 收到群组论坛的人工改名事件后自动锁定;私聊话题无法依赖该事件检测人工改名,请使用 `/topicname off`。开关与命名状态保存在状态目录的 `topic-titles.json`,重启后保留。
301
310
 
311
+ ### 分段回复
312
+
313
+ 在账号「设置」里将「分段回复」选为「分段发送」后,助手会把一次回复按分隔标记拆成多条短消息逐条发送,读起来更像连着说几句。默认为「完整发送」,关闭时行为与以前一致。目前只在 QQ 渠道开放(已按逐条投递验证),其他渠道不显示该选项,也不会切分。
314
+
315
+ - **发送间隔**:填写最小与最大间隔(秒,0–60)。每条消息(包括第一条)的发送间隔都从这个区间里随机取;上限低于下限时不会保存,改动保存后立即生效。
316
+ - **分隔标记**:由插件配置 `segmentMarker` 指定,默认 `<<<MSG>>>`,必须独占一行;围栏代码块里的同名标记不会触发分段,代码示例不会被拆散。
317
+ - **配置位置**:开关和间隔按账号保存在 `channels.json`;插件配置 `segmentReply` 可作为所有账号的默认值,账号设置优先。分段发送中途失败就停止,不整条重发,避免重复消息。
318
+
302
319
  ### Slack 接入步骤
303
320
 
304
321
  Slack 走 Socket Mode 长连接,不需要公网地址,也不用配置请求网址:
@@ -344,7 +361,7 @@ Slack 走 Socket Mode 长连接,不需要公网地址,也不用配置请求
344
361
  | 用户准入 | 群聊不用绑定,只需 @。每个账号可选择「仅已批准用户」或「允许所有私聊用户」;默认仅批准用户可用,微信 / 飞书 / Lark / QQ 扫码者会自动加入该账号白名单 |
345
362
  | 管理接口 | `/api/dsh-im-connect`;通过宿主 `connection.requestRejection` 验证 Host、Origin 和 Cookie,本机也须登录;认证不可用返回 503,写接口保留 JSON、客户端请求头和 1 MiB 限制 |
346
363
  | 敏感字段 | 包括微信 token 在内均优先写入 DSH `ctx.credentials`;没有该服务时落到 `%DSH_HOME%\dsh-im-connect\secrets.json`(明文,仅限当前用户,禁止同步或分享) |
347
- | 账号状态 | `channels.json` 按账号保存工作区、模型、权限、私聊准入、发送方式、启用状态和凭据引用,不保存明文 Secret |
364
+ | 账号状态 | `channels.json` 按账号保存工作区、模型、权限、私聊准入、发送方式、分段回复开关与发送间隔、启用状态和凭据引用,不保存明文 Secret |
348
365
  | 浏览器回包 | 不返回 token、secret、App Secret 或内部异常详情 |
349
366
  | 微信协议 | 只走腾讯官方 iLink,不使用逆向个人微信协议 |
350
367
  | 工具批准 | 在绑定该会话的聊天里由任务发起者回复「批准 / 拒绝」;私聊准入只决定谁能对话,不再单独卡审批,也不会交回网页。5 分钟无回复按取消结束,不把期间的其他文字送进下一轮 |
@@ -0,0 +1,27 @@
1
+ <svg width="36" height="36" viewBox="0 0 36 36" fill="none" xmlns="http://www.w3.org/2000/svg">
2
+ <defs>
3
+ <linearGradient id="dsh_svg_im_wechat" x1="4" y1="6" x2="24" y2="24" gradientUnits="userSpaceOnUse">
4
+ <stop stop-color="#10B981"/>
5
+ <stop offset="1" stop-color="#059669"/>
6
+ </linearGradient>
7
+ <linearGradient id="dsh_svg_im_feishu" x1="12" y1="12" x2="32" y2="30" gradientUnits="userSpaceOnUse">
8
+ <stop stop-color="#3B82F6"/>
9
+ <stop offset="1" stop-color="#1D4ED8"/>
10
+ </linearGradient>
11
+ </defs>
12
+ <!-- Primary Chat Bubble (WeChat Green Style, Top-Left) -->
13
+ <path d="M6 10C6 7.79 7.79 6 10 6H20C22.21 6 24 7.79 24 10V16C24 18.21 22.21 20 20 20H13L8 23.5V20C6.9 20 6 19.1 6 18V10Z" fill="url(#dsh_svg_im_wechat)"/>
14
+ <!-- Message Lines in Green Bubble -->
15
+ <line x1="10" y1="11" x2="19" y2="11" stroke="#FFFFFF" stroke-width="1.8" stroke-linecap="round"/>
16
+ <line x1="10" y1="15" x2="15" y2="15" stroke="#FFFFFF" stroke-width="1.8" stroke-linecap="round"/>
17
+
18
+ <!-- Secondary Chat Bubble (Feishu/Lark Blue Style, Bottom-Right) -->
19
+ <path d="M14 18C14 16.34 15.34 15 17 15H27C28.66 15 30 16.34 30 18V24C30 25.66 28.66 27 27 27H24V29.8L20 27H17C15.34 27 14 25.66 14 24V18Z" fill="url(#dsh_svg_im_feishu)" stroke="#FFFFFF" stroke-width="1.5"/>
20
+ <!-- Message Dots in Blue Bubble -->
21
+ <circle cx="19" cy="21" r="1.2" fill="#FFFFFF"/>
22
+ <circle cx="22" cy="21" r="1.2" fill="#FFFFFF"/>
23
+ <circle cx="25" cy="21" r="1.2" fill="#FFFFFF"/>
24
+
25
+ <!-- Dynamic Communication Sync Ring / Lightning in Center -->
26
+ <path d="M12 25C10 26 8 25 7 24M28 11C29 10 31 11 31 12" stroke="#F59E0B" stroke-width="1.5" stroke-linecap="round"/>
27
+ </svg>