dsh-workbuddy-connect 0.5.4 → 0.6.0

package/README.en.md

@@ -20,7 +20,15 @@ Both the CN **WorkBuddy** and the international **WorkBuddy AI** apps are suppor
 
 - **Reasoning levels**: levels explicitly declared by WorkBuddy appear directly — for example, GLM-5.3 and GLM-5.3-Flash offer low / high / max. For some models that do not declare selectable levels, Web and Desktop provide a **Reasoning levels** control in the model picker for a manual check. It sends a few requests and may consume credit. Models without a check result or selectable levels continue to use WorkBuddy's default.
 
-- **Status and detection**: Settings → Plugins → the matching card shows the account, token validity, remaining credit, and model offers. It also lets you refresh the model list manually and shows whether the current list came from the upstream or from the built-in fallback, and provides manual reasoning-level detection for eligible models.
+- **Status and detection**: Settings → Plugins → the matching card shows the account, token validity, remaining credit, and model offers (on DSH `0.1.6+` the entry lives in the left sidebar Plugins panel — see the version table below). It also lets you refresh the model list manually and shows whether the current list came from the upstream or from the built-in fallback, and provides manual reasoning-level detection for eligible models.
+
+- **Model visibility**: both WorkBuddy and WorkBuddy AI cards (Context window tab) let you check which models appear in the model picker. Hidden lists are **saved per signed-in account**: switching accounts switches to that account's own list, switching back restores it; new accounts and newly added models are visible by default. Hiding only affects pickability — **existing chats using a hidden model keep working**.
+
+![Model visibility in the context-window list (DSH 0.1.6+ plugin configuration page)](assets/6.png)
+
+The same UI works unchanged inside the DSH 0.1.5 settings cards:
+
+![Model visibility in a DSH 0.1.5 settings card](assets/7.png)
 
 - **Enterprise credit**: on the CN product, enterprise accounts (non-empty `enterpriseId`) read their cycle quota from the enterprise billing endpoint, and the card shows an "enterprise quota" row with the cycle reset time.
 
@@ -48,18 +56,46 @@ For models without declared levels, Web and Desktop instead use user-authorized,
 
 Prerequisite: the WorkBuddy desktop app is installed and signed in. The plugin reuses the app's sign-in state and follows account switches automatically; the same applies to the international WorkBuddy AI app, and the two do not affect each other.
 
-**Match the plugin version to your DSH core** — a mismatched combination fails to start DSH:
+**Match the plugin version to your DSH core** — from **`0.6.0`** on, one plugin version spans both core generations, removing the per-version pairing; earlier releases still pair one-to-one, and a mismatched combination fails to start DSH:
 
 | Plugin | Required DSH core | Desktop app |
 |---|---|---|
-| **0.3.2+** (international support since `0.5.0`) | `0.1.5-rc.1` or newer | `2.0.7`+ (bundled core `0.1.5-rc.1`) |
+| **0.6.0 (dual-UI adaptive)** | `0.1.5-rc.1` / `rc.2` / `rc.3`; the `0.1.6-alpha` line (incl. `alpha.1` / `alpha.2`) and `0.1.6` stable; verified against `0.1.7-alpha.1` (`0.1.7` stable is inside the range too). **Newer prereleases (e.g. `0.1.8-alpha.x`) are NOT covered automatically** — the plugin must extend its peer range first | `2.0.7`+ works today; desktop builds bundling `0.1.6+` will work too |
+| **0.3.2 – 0.5.4** (international support since `0.5.0`) | the `0.1.5-rc.1` line only (no `0.1.6+`; see [#41](https://github.com/corrinehu/dsh-workbuddy-connect/issues/41)) | `2.0.7`+ (bundled core `0.1.5-rc.1`) |
 | **0.3.0 – 0.3.1** | `0.1.2-rc.1` | `2.0.5` |
 | **0.2.6** | `0.1.1-rc.2` (older line) | `2.0.3` / `2.0.4` |
 
-- On DSH `0.1.5-rc.1` or newer, just install the latest: `dsh plugin --profile web add dsh-workbuddy-connect`
+- **`0.6.0` does not require upgrading to DSH `0.1.6` just to install WorkBuddy Connect**: the plugin adapts to whichever configuration surface the host actually provides at load time — `0.1.5` and `0.1.6+` each get their own UI, independently.
+- **Where the cards live depends on the DSH version** — each generation has its own place:
+
+  ```text
+  DSH 0.1.5 + this plugin
+  ├─ Settings → Models
+  │   └─ no WorkBuddy rows ← unified with 0.1.6+ (only plugins ≤0.5.4 still showed those old
+  │                            configurable-provider rows)
+  ├─ Settings → Plugins
+  │   ├─ DSH WorkBuddy Connect      ✅ config card (CN)
+  │   └─ DSH WorkBuddy AI Connect   ✅ config card (international)
+  └─ chat model picker
+      └─ WorkBuddy / WorkBuddy AI groups ✅
+
+  DSH 0.1.6+ + this plugin
+  ├─ Settings → Models
+  │   └─ no WorkBuddy rows          ← intentional, consistent across both generations
+  ├─ Settings → Built-in Plugins
+  │   └─ workbuddy-connect          ← read-only inventory (runtime status), no config entry
+  ├─ main UI → Plugins → workbuddy-connect → View
+  │   ├─ DSH WorkBuddy Connect      ✅ new config entry (CN)
+  │   └─ DSH WorkBuddy AI Connect   ✅ new config entry (international)
+  └─ chat model picker
+      └─ WorkBuddy / WorkBuddy AI groups ✅
+  ```
+
+- From `0.6.0` on, the Models settings page no longer shows the non-editable WorkBuddy / WorkBuddy AI cards (consistent across both core generations); the model picker, `/model`, and chat calls are unaffected.
+- On DSH `0.1.5` / `0.1.6` / `0.1.7`, just install the latest: `dsh plugin --profile web add dsh-workbuddy-connect`
 - Still on DSH `0.1.2-rc.1`? Stay on `0.3.1`: `dsh plugin --profile web add dsh-workbuddy-connect@0.3.1`
 - Still on DSH `0.1.1-rc.2`? Stay on the older release: `dsh plugin --profile web add dsh-workbuddy-connect@0.2.6`
-- The desktop app has bundled `0.1.5-rc.1` since `2.0.7`, so it can use `0.3.2` and newer directly; `2.0.5` and earlier apps (bundled `0.1.2-rc.1`) should stay on `0.3.1`
+- The desktop app has bundled `0.1.5-rc.1` since `2.0.7`, so it can use the latest plugin directly; `2.0.5` and earlier apps (bundled `0.1.2-rc.1`) should stay on `0.3.1`
 
 The plugin runs under all three DSH interfaces: **Web**, **Desktop**, and **TUI**. Pick the install command that matches the profile you use.
 

package/README.md

@@ -28,7 +28,15 @@
 - **推理档位**：WorkBuddy 明确声明的档位会直接显示，例如 GLM-5.3 和 GLM-5.3-Flash 可选 low / high / max。对于部分没有声明可选档位的模型，Web 和 Desktop 可在模型选择器中点击「推理等级」手动检测；检测会发送少量请求，可能消耗积分。未检测或没有可用档位的模型仍使用 WorkBuddy 的默认档位。
 
 
-- **信息查看与检测**：设置 → 插件 → 对应卡片可查看账号、令牌有效期、剩余积分和模型优惠；也可以手动刷新模型列表，并在卡片上看到当前列表来自上游还是内置兜底。对于可检测模型，也可以在这里手动检测推理档位。
+- **信息查看与检测**：设置 → 插件 → 对应卡片可查看账号、令牌有效期、剩余积分和模型优惠（DSH `0.1.6+` 上入口在左侧栏「插件」面板，见下方版本对应一节）；也可以手动刷新模型列表，并在卡片上看到当前列表来自上游还是内置兜底。对于可检测模型，也可以在这里手动检测推理档位。
+
+- **模型显隐**：WorkBuddy 与 WorkBuddy AI 都可以在对应卡片的「上下文窗口」标签里勾选要在模型选择器中显示的模型。隐藏配置**按登录账号分别保存**：切换账号自动切换各自的配置，切回后恢复；新账号和新上架的模型默认显示。隐藏只影响选择器里的可选性，**正在使用该模型的已有会话不受影响**。
+
+![上下文窗口列表里的模型显隐（DSH 0.1.6+ 插件配置页）](assets/6.png)
+
+同一份界面在 DSH 0.1.5 的设置卡片中原样生效：
+
+![DSH 0.1.5 设置卡片中的模型显隐](assets/7.png)
 
 - **企业账号积分**：国内版企业账号（`enterpriseId` 非空）走企业专用计费接口读取周期额度，卡片显示「企业额度」与周期重置时间。
 
@@ -58,18 +66,45 @@ WorkBuddy 中模型的推理档位信息目前分散在上游接口与客户端
 
 前置：已安装并登录 WorkBuddy 桌面 App。插件复用 App 的登录状态，账号切换自动跟随；装了国际版 WorkBuddy AI 的同样适用，两版互不影响。
 
-**版本对应（重要）**：本插件与 DSH 核心版本一一对应，不可混用——不匹配的组合会导致 DSH 启动失败：
+**版本对应（重要）**：自 **`0.6.0`** 起，同一个插件版本横跨两代 DSH 核心，安装时无需再逐版本对照；更早的已发布版本仍与核心一一对应，不可混用——不匹配的组合会导致 DSH 启动失败：
 
 | 插件版本 | 要求的 DSH 核心 | 桌面 App |
 |---|---|---|
-| **0.3.2+**（国际版支持自 `0.5.0`） | `0.1.5-rc.1` 及以上 | `2.0.7`+（内置核心已跟进 `0.1.5-rc.1`） |
+| **0.6.0（双界面自适应）** | `0.1.5-rc.1` / `rc.2` / `rc.3`；`0.1.6-alpha` 系列（含 `alpha.1` / `alpha.2`）与 `0.1.6` 正式版；已实测 `0.1.7-alpha.1`（`0.1.7` 正式版同样在范围内）。**更新的 prerelease（如 `0.1.8-alpha.x`）不自动覆盖**，需插件显式跟进 peer range 后才支持 | `2.0.7`+ 可直接使用；搭载 `0.1.6+` 核心的桌面版发布后同样适用 |
+| **0.3.2 – 0.5.4**（国际版支持自 `0.5.0`） | `0.1.5-rc.1` 系列（不支持 `0.1.6+`，见 [#41](https://github.com/corrinehu/dsh-workbuddy-connect/issues/41)） | `2.0.7`+（内置核心已跟进 `0.1.5-rc.1`） |
 | **0.3.0 – 0.3.1** | `0.1.2-rc.1` | `2.0.5` |
 | **0.2.6** | `0.1.1-rc.2`（旧线） | `2.0.3` / `2.0.4` |
 
-- DSH `0.1.5-rc.1` 及以上的用户，正常安装最新版即可：`dsh plugin --profile web add dsh-workbuddy-connect`
+- **计划中的 `0.6.0` 不要求为了安装 WorkBuddy Connect 强制升级到 DSH `0.1.6`**：插件在加载时按宿主实际提供的配置入口自适应，`0.1.5` 与 `0.1.6+` 各自走各自的界面，互不干扰。
+- **配置入口随 DSH 版本不同**，两代各就各位：
+
+  ```text
+  DSH 0.1.5 + 本插件
+  ├─ 设置 → 模型
+  │   └─ 不显示 WorkBuddy 两行 ← 与 0.1.6+ 统一（≤0.5.4 旧版插件才显示那两行旧 configurable-provider 条目）
+  ├─ 设置 → 插件
+  │   ├─ DSH WorkBuddy Connect      ✅ 配置卡片（国内版）
+  │   └─ DSH WorkBuddy AI Connect   ✅ 配置卡片（国际版）
+  └─ 聊天模型选择器
+      └─ WorkBuddy / WorkBuddy AI 分组 ✅
+
+  DSH 0.1.6+ + 本插件
+  ├─ 设置 → 模型
+  │   └─ 不显示 WorkBuddy 两行      ← 有意如此，两代行为统一
+  ├─ 设置 → 内置插件
+  │   └─ workbuddy-connect          ← 只读清单（运行状态），无配置入口，别找错地方
+  ├─ 主界面 → 插件 → workbuddy-connect → 查看
+  │   ├─ DSH WorkBuddy Connect      ✅ 新配置入口（国内版）
+  │   └─ DSH WorkBuddy AI Connect   ✅ 新配置入口（国际版）
+  └─ 聊天模型选择器
+      └─ WorkBuddy / WorkBuddy AI 分组 ✅
+  ```
+
+- 自 `0.6.0` 起，Models 设置页不再显示 WorkBuddy / WorkBuddy AI 的不可编辑卡片（两代核心行为一致）；模型选择器、`/model` 与对话调用不受影响。
+- DSH `0.1.5` / `0.1.6` / `0.1.7` 的用户，安装最新版即可：`dsh plugin --profile web add dsh-workbuddy-connect`
 - 还在用 DSH `0.1.2-rc.1` 的用户，请停留在 `0.3.1`：`dsh plugin --profile web add dsh-workbuddy-connect@0.3.1`
 - 还在用 DSH `0.1.1-rc.2` 的用户，请停留在 `0.2.6`：`dsh plugin --profile web add dsh-workbuddy-connect@0.2.6`
-- 桌面 App 自 `2.0.7` 起内置核心已是 `0.1.5-rc.1`，可直接使用 `0.3.2` 及以上版本；`2.0.5` 及更早的 App（内置 `0.1.2-rc.1`）请继续使用 `0.3.1`
+- 桌面 App 自 `2.0.7` 起内置核心已是 `0.1.5-rc.1`，可直接使用最新版插件；`2.0.5` 及更早的 App（内置 `0.1.2-rc.1`）请继续使用 `0.3.1`
 
 插件在三种 DSH 界面下均可运行：**Web**、**Desktop**、**TUI**。根据你使用的 profile 选对应命令安装。
 

package/lib/bin.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { E as WorkBuddyUpstreamClient, J as resolveAppVersion, b as WorkBuddyCredentialStore, f as WORKBUDDY_CONNECT_VERSION, g as FALLBACK_WORKBUDDY_MODELS, h as FALLBACK_WORKBUDDY_AI_MODELS, i as variantFor, l as readHostHeartbeat, n as CN_VARIANT, r as WORKBUDDY_VARIANTS, s as isHeartbeatProcessAlive, u as workbuddyHostHeartbeatPath } from "./variants-XUStsapF.js";
+import { D as WorkBuddyUpstreamClient, Y as resolveAppVersion, b as WorkBuddyCredentialStore, f as WORKBUDDY_CONNECT_VERSION, g as FALLBACK_WORKBUDDY_MODELS, h as FALLBACK_WORKBUDDY_AI_MODELS, i as variantFor, l as readHostHeartbeat, n as CN_VARIANT, r as WORKBUDDY_VARIANTS, s as isHeartbeatProcessAlive, u as workbuddyHostHeartbeatPath } from "./variants-CnrmSn0Q.js";
 import { realpathSync } from "node:fs";
 import { fileURLToPath } from "node:url";
 //#region src/bin.ts
@@ -46,9 +46,12 @@ async function doctor(jsonOutput, variant) {
 	const store = makeStore(variant);
 	const status = await store.status();
 	const desktopPresent = await store.desktopFilePresent();
+	const desktopFormat = await store.desktopAuthFormat();
+	const desktopPath = await store.resolvedDesktopAuthPath() ?? store.desktopAuthPath();
 	const heartbeat = await readHostHeartbeat();
 	const hostAlive = heartbeat !== void 0 && isHeartbeatProcessAlive(heartbeat);
 	const appVersion = variant.region === "global" ? await resolveAppVersion() : void 0;
+	const decryptionNote = status.state === "signed-out" && desktopFormat === "encrypted" && status.reason !== void 0 ? `Encrypted desktop credential could not be used: ${status.reason}` : void 0;
 	const report = {
 		schemaVersion: JSON_SCHEMA_VERSION,
 		package: "dsh-workbuddy-connect",
@@ -57,8 +60,9 @@ async function doctor(jsonOutput, variant) {
 		provider: variant.id,
 		displayName: variant.displayName,
 		desktopAuthFile: {
-			path: store.desktopAuthPath() ?? `(no platform default; set ${variant.env})`,
-			present: desktopPresent
+			path: desktopPath ?? `(no platform default; set ${variant.env})`,
+			present: desktopPresent,
+			format: desktopFormat
 		},
 		ownAuthFile: ownAuthPath(variant),
 		...appVersion === void 0 ? {} : { catalogUserAgent: {
@@ -78,15 +82,18 @@ async function doctor(jsonOutput, variant) {
 		signIn: status.state,
 		fallbackModels: fallbackCount(variant),
 		hints: [
-			...status.state === "signed-in" ? [] : [`Sign in once in the ${variant.appName} desktop app, then run status again.`],
+			...decryptionNote !== void 0 ? [decryptionNote] : status.state === "signed-out" ? [`Sign in once in the ${variant.appName} desktop app, then run status again.`] : [],
 			...desktopPresent ? [] : [`No ${variant.appName} desktop auth file at the expected path; set ${variant.env} if it lives elsewhere.`],
 			...hostAlive ? [] : ["Host bundle not running in this DSH profile (or the process exited). The browser card and provider are unavailable until DSH starts the plugin."]
 		]
 	};
-	if (jsonOutput) printJson(report);
+	if (jsonOutput) printJson({
+		...report,
+		...decryptionNote === void 0 ? {} : { decryptionNote }
+	});
 	else process.stdout.write([
 		`${variant.displayName} Connect ${WORKBUDDY_CONNECT_VERSION} on ${process.version}`,
-		`Desktop auth file: ${report.desktopAuthFile.present ? "present" : "missing"} (${report.desktopAuthFile.path})`,
+		`Desktop auth file: ${report.desktopAuthFile.present ? "present" : "missing"} — ${desktopFormat} (${report.desktopAuthFile.path})`,
 		`Host bundle: ${hostAlive ? `running (pid ${heartbeat.pid})` : heartbeat !== void 0 ? "stale heartbeat (process exited)" : "not started"}`,
 		`Sign-in state: ${report.signIn}`,
 		`Static fallback models: ${report.fallbackModels}`,