dsh-connect-trae 4.5.1 → 4.5.2

package/CHANGELOG.md

@@ -1,5 +1,46 @@
 # Changelog
 
+## 4.5.2 (2026-10-25)
+
+> **思考档位不再被吞，也不再被谎报。** 插件原先只认识三档，未知档位一律按 `high`
+> 发出去——用户选 Max、实际收到 high，无报错也无日志。这一版把词表与 Trae 客户端
+> 对齐（`low / medium / high / extra_high / max`），并把「不认识的档位」从谎报改成
+> 丢弃，让上游用它自己的默认值。
+>
+> 词表变宽，**声称没变**：能选哪些档位仍然只取决于上游为该模型实际下发的
+> `options`，所以今天只发三档的模型不会凭空多出 Max。
+
+### 修复
+
+- **思考档位词表配平，未知档位不再静默降档成 high**（#60）。
+  - **三处吞档位**：解析侧 `EFFORT_MAP` / `TRAE_REASONING_EFFORTS` 缺 `medium` 与
+    `max`；`toPiModel` 的 `thinkingLevelMap` 把 `minimal / medium / max` 硬编码成
+    `null`；反向映射写成三元链
+    `effort === 'low' ? 'light' : effort === 'xhigh' ? 'extra_high' : 'high'`。
+  - **最坏的是第三处**：任何未预期档位都被映射成 `high` 发给上游。Trae 客户端自己
+    认识五档（`reasoning_effort.{low,medium,high,extra_high,max}`），并按 agent model
+    灰度下发，所以上游哪天发 `max`，用户选 Max 就会被静默降成 high。**静默降档比
+    不给选择器更坏**——它给出一个便宜了、但用户没要的答案。
+  - **改法**：反向映射抽成 `WIRE_EFFORT_MAP` 查表 + `wireEffortsOf()`，三处调用点
+    统一走它（报告人点到两处，第三处在 wire 行提升的分支里，一起改才不会有同一份
+    目录两种行为）。查不到即**丢弃**，而不是猜一个默认值。
+  - **实测**（2026-10-25，本机 CN 凭据，98 行目录）：当前 `options` 只有
+    `["light","high"]`、`["high","extra_high"]`、`["light","high","extra_high"]`
+    三种，`max` 尚未下发——所以这是「今天就备好、明天才用上」，不是伪造档位。
+  - 测试：新增 10 例（词表、丢弃未知档位、既有三档逐字不变、`discoveredCatalog`
+    同步、不伪造档位、`thinkingLevelMap` 按模型而非硬编码）。三处均做变异验证：
+    恢复旧映射 → 5 例红；恢复硬编码 `null` → 1 例红；去掉解析侧新键 → 1 例红。
+  - 贡献者：[@ahian-lee](https://github.com/ahian-lee)（issue #60，附诊断与补丁）。
+
+### 文档
+
+- **卡片模型栏写明「上下文预算只影响 DSH 侧」**（#60 的顺带问题）。
+  - 每行显示的是 Trae 自己公布的最大窗口，而下面的预算单选只写 DSH 的本地预算；
+    请求体里既没有窗口字段、也没有 `max_mode`，所以把预算提到 1M 并不会让上游按
+    1M 服务。原先的标签读起来像「已经放开到 1M」。
+  - 上游是否接受 `v2_max_mode_enabled` 这类字段**尚未取证**，所以这次不动请求体
+    （乱加字段可能让每次请求 400），只把事实说出来：常驻说明，不用悬停提示。
+
 ## 4.5.1 (2026-10-25)
 
 > **只在租户池上架的模型不再隐形。** 插件的模型目录只问了 `solo.trae.cn` 一处，

package/lib/client.js

@@ -5659,6 +5659,7 @@ window.__ModuleLoader__.load({
 																	}), /* @__PURE__ */ (0, react_jsx_runtime.jsx)("fieldset", {
 																		className: "dsm-trae-context-budget",
 																		"aria-label": t("row.contextBudget"),
+																		title: t("row.contextBudgetHint"),
 																		children: contextBudgetOptions(model).map((option) => {
 																			const selectable = model.maxContextWindow !== void 0;
 																			const checked = (activeContextBudgets[model.id] ?? model.contextWindow) === option;
@@ -5726,6 +5727,10 @@ window.__ModuleLoader__.load({
 													})
 												]
 											}),
+											/* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
+												className: "dsm-trae-model-capability-note",
+												children: t("row.contextBudgetHint")
+											}),
 											/* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
 												className: "dsm-trae-model-capability-note",
 												children: t("row.modelCapabilityPending")
@@ -6898,6 +6903,7 @@ window.__ModuleLoader__.load({
 			"row.veilSaving": "Saving changes…",
 			"row.modelContext": "Max context {context}",
 			"row.contextBudget": "DSH context budget",
+			"row.contextBudgetHint": "Affects the DSH-side context budget only. The plugin does not send a window or Max-mode field upstream, so this does not change the window Trae serves the request with.",
 			"row.modelOutput": "Output {output}",
 			"row.modelImage": "Image",
 			"row.modelImageAuto": "Enabled automatically: Trae marks this model multimodal.",
@@ -7277,6 +7283,7 @@ window.__ModuleLoader__.load({
 			"row.veilSaving": "正在保存更改…",
 			"row.modelContext": "最大上下文 {context}",
 			"row.contextBudget": "DSH 上下文预算",
+			"row.contextBudgetHint": "只影响 DSH 侧的上下文预算。插件不会向上游发送窗口或 Max 模式字段，所以这不会改变 Trae 实际服务这次请求所用的窗口。",
 			"row.modelOutput": "最大输出 {output}",
 			"row.modelImage": "图片",
 			"row.modelImageAuto": "已自动开启：Trae 把该模型标为多模态。",

package/lib/index.d.ts

@@ -44,7 +44,23 @@ interface TraeActivityDiscount {
 }
 //#endregion
 //#region src/reasoning.d.ts
-declare const TRAE_REASONING_EFFORTS: readonly ["minimal", "low", "medium", "high", "xhigh"];
+/**
+ * The DSH thinking levels this plugin can carry, in ascending order.
+ *
+ * `max` is the fifth level Trae's own client advertises — its bundle ships the
+ * i18n keys `trae-chat-core.model.reasoning_effort.{low,medium,high,extra_high,max}`
+ * and `ai.model.reasoning_effort.{low,medium,high,xhigh,max}`, and publishes the
+ * per-model list from a remote config (`AI.agent.model.reasoning_effort_level_by_agent_model_v2`).
+ * Leaving it out of this list meant a level the vendor could start serving was
+ * filtered away at PARSE time, before anything downstream could decide (issue
+ * #60). Listing it does not fabricate the level: `supported` is still built
+ * only from what the upstream response actually contains, so a model that does
+ * not advertise `max` never offers it.
+ *
+ * `minimal` is kept for the same reason in reverse — it is a DSH level, so the
+ * type must be able to represent it even though no CN model has advertised it.
+ */
+declare const TRAE_REASONING_EFFORTS: readonly ["minimal", "low", "medium", "high", "xhigh", "max"];
 type TraeReasoningEffort = typeof TRAE_REASONING_EFFORTS[number];
 interface TraeReasoningCapability {
   supported: readonly TraeReasoningEffort[];

package/lib/index.js

@@ -282,6 +282,53 @@ function displayKey(name) {
 	return name.trim().toLowerCase();
 }
 /**
+* DSH thinking level -> the `reasoning_effort` name Trae's wire accepts.
+*
+* The INVERSE of `EFFORT_MAP` in `model-metadata.ts`, and it must stay an exact
+* mirror of it: a level this table does not name has no wire spelling, so it is
+* DROPPED rather than guessed (issue #60).
+*
+* The previous form was a ternary chain ending in a bare `'high'`:
+*
+*     effort === 'low' ? 'light' : effort === 'xhigh' ? 'extra_high' : 'high'
+*
+* so EVERY unnamed level was sent as `high`. That is not a harmless default: it
+* is a silent downgrade. Trae's own vocabulary carries five levels
+* (`low / medium / high / extra_high / max`, verified in the client bundle's
+* `reasoning_effort` i18n keys), and its remote config publishes the list per
+* model (`AI.agent.model.reasoning_effort_level_by_agent_model_v2`). The day
+* upstream starts advertising `max`, a user picking Max would have sent `high`
+* — no error, no log, and a cheaper answer than the one they asked for. A
+* dropped field lets the upstream apply its own default, which is at least the
+* model's real behaviour instead of a wrong claim about it.
+*
+* Measured 2026-10-25 on a live CN credential (98 directory rows): options are
+* `["light","high"]`, `["high","extra_high"]`, `["light","high","extra_high"]`
+* or absent — `max` is not published YET, which is exactly why this must not
+* wait for it to be.
+*/
+const WIRE_EFFORT_MAP = {
+	low: "light",
+	medium: "medium",
+	high: "high",
+	xhigh: "extra_high",
+	max: "max"
+};
+/**
+* Map a model's advertised levels to their wire names, dropping unnamed ones.
+*
+* `flatMap` rather than `map` + a placeholder: an unmappable level must not
+* produce an entry at all, because every consumer reads "is there a value here"
+* as "may this level be sent" (see `thinkingLevelMap` in `adapter.ts` and the
+* `delete input['reasoning_effort']` fallback in `solo-bridge.ts`).
+*/
+function wireEffortsOf(supported) {
+	return Object.fromEntries(supported.flatMap((effort) => {
+		const wire = WIRE_EFFORT_MAP[effort];
+		return wire === void 0 ? [] : [[effort, wire]];
+	}));
+}
+/**
 * Merge the two Trae model sources into one authoritative catalog.
 *
 * `remote` (the solo.trae.cn `/models` directory) is the authoritative model
@@ -360,7 +407,7 @@ function mergeTraeModelSources(remote, wire) {
 			reasoningSupported: model.reasoningSupported,
 			...model.reasoning === void 0 ? {} : {
 				reasoning: model.reasoning,
-				reasoningEfforts: Object.fromEntries(model.reasoning.supported.map((effort) => [effort, effort === "low" ? "light" : effort === "xhigh" ? "extra_high" : "high"]))
+				reasoningEfforts: wireEffortsOf(model.reasoning.supported)
 			},
 			...wireModel !== void 0 && wireModel.id !== "" && wireModel.id !== model.id ? { wireConfigName: wireModel.id } : {},
 			...wireFunction === void 0 ? {} : { wireFunction }
@@ -433,7 +480,7 @@ function mergeTraeModelSources(remote, wire) {
 					supported: [...wireModel.reasoning.supported],
 					...wireModel.reasoning.defaultEffort === void 0 ? {} : { defaultEffort: wireModel.reasoning.defaultEffort }
 				},
-				reasoningEfforts: Object.fromEntries(wireModel.reasoning.supported.map((effort) => [effort, effort === "low" ? "light" : effort === "xhigh" ? "extra_high" : "high"]))
+				reasoningEfforts: wireEffortsOf(wireModel.reasoning.supported)
 			},
 			...wireModel.function === void 0 ? {} : { wireFunction: wireModel.function }
 		});
@@ -507,7 +554,7 @@ function discoveredCatalog(models) {
 		reasoningSupported: model.reasoningSupported,
 		...model.reasoning === void 0 ? {} : {
 			reasoning: model.reasoning,
-			reasoningEfforts: Object.fromEntries(model.reasoning.supported.map((effort) => [effort, effort === "low" ? "light" : effort === "xhigh" ? "extra_high" : "high"]))
+			reasoningEfforts: wireEffortsOf(model.reasoning.supported)
 		}
 	});
 	return result;
@@ -836,14 +883,28 @@ function toPiModel(info, baseUrl, providerId, withRate = true) {
 			cacheWrite: 0
 		},
 		reasoning: info.reasoningEfforts !== void 0,
-		...info.reasoningEfforts === void 0 ? {} : { thinkingLevelMap: {
+		...info.reasoningEfforts === void 0 ? {} : { 
+		/**
+		* Which DSH levels this model may be asked for, and under which wire name.
+		*
+		* Every level is read from the model's OWN advertised capability, never
+		* hardcoded. `minimal / medium / max` used to be pinned to `null`, so a
+		* level the upstream published could not be selected even after it was
+		* parsed — the second of the three places issue #60 reported. `null`
+		* still means "not offered", which is what a model that does not
+		* advertise the level reports: nothing here fabricates a level.
+		*
+		* `off` stays `null` deliberately: Trae's wire has no "no reasoning"
+		* spelling, so an explicit off is not something this provider can send.
+		*/
+thinkingLevelMap: {
 			off: null,
-			minimal: null,
+			minimal: info.reasoningEfforts.minimal ?? null,
 			low: info.reasoningEfforts.low ?? null,
-			medium: null,
+			medium: info.reasoningEfforts.medium ?? null,
 			high: info.reasoningEfforts.high ?? null,
 			xhigh: info.reasoningEfforts.xhigh ?? null,
-			max: null
+			max: info.reasoningEfforts.max ?? null
 		} },
 		...info.contextWindow === void 0 ? {} : { contextWindow: info.contextWindow },
 		...info.maxTokens === void 0 ? {} : { maxTokens: info.maxTokens },
@@ -4752,12 +4813,29 @@ function parseTraeActivityDiscount(value) {
 }
 //#endregion
 //#region src/reasoning.ts
+/**
+* The DSH thinking levels this plugin can carry, in ascending order.
+*
+* `max` is the fifth level Trae's own client advertises — its bundle ships the
+* i18n keys `trae-chat-core.model.reasoning_effort.{low,medium,high,extra_high,max}`
+* and `ai.model.reasoning_effort.{low,medium,high,xhigh,max}`, and publishes the
+* per-model list from a remote config (`AI.agent.model.reasoning_effort_level_by_agent_model_v2`).
+* Leaving it out of this list meant a level the vendor could start serving was
+* filtered away at PARSE time, before anything downstream could decide (issue
+* #60). Listing it does not fabricate the level: `supported` is still built
+* only from what the upstream response actually contains, so a model that does
+* not advertise `max` never offers it.
+*
+* `minimal` is kept for the same reason in reverse — it is a DSH level, so the
+* type must be able to represent it even though no CN model has advertised it.
+*/
 const TRAE_REASONING_EFFORTS = [
 	"minimal",
 	"low",
 	"medium",
 	"high",
-	"xhigh"
+	"xhigh",
+	"max"
 ];
 function parseReasoningCapability(value) {
 	if (typeof value !== "object" || value === null || Array.isArray(value)) return void 0;
@@ -5863,10 +5941,31 @@ function parseFeatures(value) {
 		return;
 	}
 }
+/**
+* Trae's wire effort name -> the DSH thinking level.
+*
+* The FORWARD half of the mapping; `WIRE_EFFORT_MAP` in `catalog.ts` is its
+* exact inverse. Both halves must name the same levels, or a level survives one
+* direction and vanishes in the other.
+*
+* `medium` and `max` are here because Trae's own client advertises them
+* (`reasoning_effort.{low,medium,high,extra_high,max}` in its i18n bundle) and
+* publishes the per-model list remotely — so the day upstream starts sending
+* either, the parser must not filter it away before anything can use it (issue
+* #60). Measured 2026-10-25 on a live CN credential, the published options were
+* only `light / high / extra_high`; these entries are therefore inert today and
+* ready tomorrow, not a claim that the levels are served now.
+*
+* An unknown name is deliberately ABSENT rather than defaulted: `parse` drops
+* it, and the reverse map drops it too, so an unrecognised level can never be
+* reported to the user or sent upstream under a name the vendor never said.
+*/
 const EFFORT_MAP = {
 	light: "low",
+	medium: "medium",
 	high: "high",
-	extra_high: "xhigh"
+	extra_high: "xhigh",
+	max: "max"
 };
 /**
 * Parse only capabilities explicitly advertised by Trae's remote model API.

package/package.json

@@ -2,7 +2,7 @@
   "name": "dsh-connect-trae",
   "displayName": "DSH Connect Trae",
   "description": "把本机登录的 Trae 模型接入 DeepSeek Harness：国内版与国际版双供应商并行，提供用量/积分概览与每日签到领取。",
-  "version": "4.5.1",
+  "version": "4.5.2",
   "author": "dingminhua",
   "copyright": "Copyright (c) 2026 LaoDing",
   "license": "MIT",