dsh-connect-trae 4.17.0 → 4.18.0

package/CHANGELOG.md

@@ -1,5 +1,98 @@
 # Changelog
 
+## 4.18.0 (2026-11-09)
+
+### 企业面板的发现层收录租户自配模型（`config_source: 2`）
+
+企业租户可以在 Trae 企业控制台配置自己的模型。Trae 自己的选择器能看到它们，插件的企业
+面板一直不列——这批行由企业侧 `get_detail_param` 返回（`config_source: 2` +
+`usage: 'chat_completion'`），**不在**企业侧 Remote 目录里，所以只有「wire 提升」一条路
+能看见它们；而提升门槛只接受 `config_source === 1`，又拒绝「`display_name` 等于
+`config_name`」的行——那恰好是租户配置模型的常见形态。两条门槛各自都足以挡掉它们。
+
+**改法。** 提升门槛接受 `2`，且这类行允许用 `config_name` 当显示名。提升改为 **opt-in**
+（`mergeTraeModelSources(..., { allowTenantConfigured })`），**只有企业面板传 `true`**：
+这些行计费落在租户池，放进消费面板等于让用户选到一个不属于自己计费面的模型。另外两条
+区域本来也取不到它们——它们的 wire 客户端钉在消费网关，那批行只出现在企业网关的名册里。
+
+**这批模型现在调用不通，这是刻意不做的部分。** 租户配置的模型属于
+`custom_openai_compatible`、客户端直连（`use_remote_service: false`、自带 base_url），
+插件没有对应传输通道，实测走 `llm_utils_chat` 返回 `4001`。本次只修发现层，通道另开
+issue 讨论——不做「静默假设能调」这种事。真要选中时，拿到的是桥接层翻译过的可读错误
+（`4001` → 该 SOLO function 不提供此模型），不是一次空白回复。
+
+### 企业版图片请求预算降到 8 MiB：网关只有 10 MiB，图文长任务不再 413
+
+**症状。** 企业版跑带图的多步任务，跑到某一步整轮失败：
+
+```
+400: {"message":"<html>...<title>413 Request Entity Too Large</title>...openresty/1.27.1.2...",
+      "type":"client","code":"client"}
+```
+
+换模型、重试、少给几张图都没用——任务只要「长到某个长度」就必然挂。实测一次真实会话：
+15 张图、base64 合计 **12.32 MB**，在第 20 步被拒。
+
+**根因。** `maxRequestImageBytes` 不是口味设置，它决定宿主要不要走「卸掉最老的图、重发」
+那条路：DSH 拿它和请求里**所有图片的 base64 总量**比较，超了就抛 `IMAGE_OFFLOAD_REQUIRED`，
+由 `dsh-compaction-image-offload` 写占位符重试。**这条链路只有在预算低于网关实测上限时才成立**；
+预算高于上限，宿主认为「装得下」，请求照发，被网关拍死在传输层——没有模型回复，无从恢复。
+
+而 `REQUEST_IMAGE_BUDGETS` 把**所有区域**都钉在宿主默认的 20 MiB，注释理由是「对齐宿主默认值」。
+那个理由对计数字段（`maxRequestImages` / `imageOffloadCountQuantum`，确是宿主契约）成立，
+对**字节上限**不成立：字节上限要对齐的是**网关**，而三个网关差 2.5 倍。
+
+**实测（2026-11-09，未鉴权探针）。** openresty 在**鉴权之前**就按 body 体积拒绝，所以状态码本身就是
+上限，且不消耗任何凭据或积分：
+
+| 网关 | 10,485,758 字节 | 10,485,762 字节 | 结论 |
+| --- | --- | --- | --- |
+| `console.enterprise.trae.cn`（`create_agent_task`） | `401` | **`413`** | 上限 10 MiB |
+| `console.enterprise.trae.cn`（`llm_utils_chat`） | `401` | **`413`** | 上限 10 MiB |
+| `trae-api-cn.mchost.guru` | `401`（测到 48 MiB） | — | 未触顶 |
+| `coresg-normal.trae.ai` | `401`（测到 20 MiB） | — | 未触顶 |
+
+**修复。** 只有企业版降到 **8 MiB**，另外两条区域保持 20 MiB：
+
+| 区域 | 改前 | 改后 |
+| --- | --- | --- |
+| `trae-enterprise` | 20 MiB | **8 MiB** |
+| `trae`（CN） | 20 MiB | 20 MiB |
+| `trae-global`（国际） | 20 MiB | 20 MiB |
+
+**为什么是 8 而不是 10。** 预算只管图片，请求还要带系统提示、工具声明和消息文本。8 MiB 留 2 MiB
+信封，而实测请求远没到这个量级（工具声明约 49 KB）。**为什么不干脆把三条都降下来**：CN 与国际
+网关实测 48 MiB / 20 MiB 都收，降它们只会白白卸掉用户本来能看到的图——那是静默的质量回退，
+不是修复。
+
+用那次失败会话的同一批图片跑宿主真实的卸载算法（`imageOffloadCountQuantum: 10`，超额按 10 的
+整数倍卸）：
+
+| | 改前（20 MiB） | 改后（8 MiB） |
+| --- | --- | --- |
+| 卸载是否触发 | 从不 | 第 13 张图时 |
+| 卸载数量 | 0 / 15 | 5 / 15 |
+| 实际发出 | ≈11.92 MiB → **413** | ≈7.99 MiB → 通过 |
+
+**没选的做法。** ① 改宿主默认值——那是所有 provider 共享的契约，不该为一个网关让步。② 直接把
+`imageOffloadCountQuantum` 调小——卸载粒度变细会增加重试轮次，而这次的问题是预算根本没触发
+卸载，与粒度无关。③ 只发占位符不重试——用户会永久失去图片内容，而重试路径本来就是为此设计的。
+
+### Tests
+
+- 新增 `tests/adapter-image-budget.spec.ts`（3 例）：企业版预算**严格小于**实测 10 MiB 上限；
+  CN 与国际**仍是**宿主默认 20 MiB；三条区域的计数上限都保持 50 / 10。
+  第一例在修复前失败（`expected 20971520 to be less than 10485760`），修复后通过。
+  另外两例钉住「不要把三条一起降下来」这条回退路径。
+- **合并时补了一条下界**（≥ 5 MiB，即实测上限的一半）：「小于 10 MiB」是个**任何更小的数**
+  都满足的断言——改成 1 MiB 也照样绿，而那会把网关收得下的图白白卸掉，正是另外两条区域
+  被保护着不许犯的那个错，只是从保守那一侧犯。实测把常量改成 `1_048_576` 会红
+  （`expected 1048576 to be greater than or equal to 5242880`）。
+- `tests/catalog.spec.ts` 新增 4 例（租户自配模型）：被提升（含 `config_name` 当显示名的形态）；
+  未 opt-in 时一行都不出（缺省与显式 `false` 两路）；`usage` 非 `chat_completion` 仍被拒；
+  空名与 `-` 仍被拒。变异验证：删掉 `allowTenantConfigured` 门控 → 第二例立刻变红。
+- 全仓 **114 个文件 / 1469 条测试**通过。
+
 ## 4.17.0 (2026-11-09)
 
 ### 自动刷新改为可选项：整个插件一个节奏，默认 5 分钟

package/README.en.md

@@ -44,6 +44,7 @@ In the account pool, open **More settings** and choose **Claude style** or **Def
 - **Three parallel providers** — the CN side registers as the `trae` provider (e.g. `DeepSeek-V4-Flash`, `DeepSeek-V4-Pro`), the enterprise side as `trae-enterprise`, and the international side as `trae-global` (the Gemini/GPT/MiniMax roster); **all three rosters appear in the DSH model picker simultaneously**: different sessions can each pick a side without interfering.
 - **Enterprise is a separate billing channel, not an alias for CN** — the same CN credential, when it belongs to a `tob_online` tenant, is served by **two** gateways: the consumer pool (billed against personal credits) and the tenant pool (billed against the enterprise allowance). Same model, two payers, so **you** choose who pays; the plugin never guesses. `trae` never touches the enterprise gateway, and `trae-enterprise` **never falls back** — a refusal is reported as a refusal instead of quietly re-running on personal credits. Enterprise is **off by default**: a personal-only account cannot use the tenant pool, so shipping it enabled would mean handing everyone a provider that fails on first use.
 - **Any panel can be switched off on its own** — each tab carries its own checkbox (CN and international checked by default, enterprise not): unchecking **withdraws that provider from the DSH model picker entirely** (not merely hiding the tab) and stops all of its requests; checking it again restores it with the account, directory, picks, and context budgets intact. If you never use the international side, just uncheck it.
+- **Enterprise models configured by the tenant now show up** — a tenant can configure models of its own in the Trae enterprise console. Those rows (`config_source: 2`) are absent from the enterprise-side Remote directory, so the plugin used to hide them entirely; they now appear on the enterprise panel and in the DSH picker. **They are not callable yet**: those models are client-direct (`use_remote_service: false`, carrying their own `base_url`) and the plugin has no transport for that channel, so selecting one fails honestly (`4001` → this SOLO function does not serve it) instead of failing silently or pretending to answer. They bill the tenant pool, which is why they appear **only on the enterprise panel**; CN and international are untouched — those two read consumer-gateway rosters to begin with.
 - **Tabbed settings card** — the card's top carries a "Domestic / Enterprise / Global" tab bar; each tab holds its own account picker, usage overview, and model management. Account, directory, selection, and unsaved drafts are fully isolated per tab — switching accounts or refreshing models on one tab never touches the other side's runtime catalog or sessions. CN and enterprise share one CN credential pool but keep **separate account bindings and model picks**: the two rosters differ (`DeepSeek-V4.1-Flash` is listed only on the enterprise pool), so picks never overwrite each other.
 - **The card then splits into "Account / Models / Diagnostics"** (learned from the sibling `dsh-connect-workbuddy`). The region row above is the **scope** — which provider this whole card is about — while these are sections of that one card: Account covers who serves, what is left, the check-in and the pool; Models covers which models to tick, image input, the context budget and Save; Diagnostics read-only lists the panel, the provider id, the serving account, both token deadlines, the catalog/enabled model counts, whether the pool and the check-in are offered, and the **verbatim** text of this panel's last reported failure. **As of 4.4.7 the diagnostics section carries one more line, "quarantined copies"**: a credential copy that could not be read — and was therefore renamed aside instead of being erased — is named there, together with how many accounts it still holds. "Where did the account I remember go?" is now answered by the card instead of by browsing `~/.dsh` for a file name; the signed-out screen shows the same notice, because that is the screen a user lands on after an account disappears. The split exists because the two halves **commit differently**: an account change lands on the click, a catalog change is a draft until Save — so a single long column put the save button three screens away from what it saves. Switching sections never refetches, never drops a half-filled model draft, and never rebuilds the pool's log. A signed-out card renders no section strip, so its one screen of instructions cannot be hidden behind a tab the user cannot see. **The Models section lays every model out at once, with no inner scrollbar** — it is not a little window scrolling inside a page that already scrolls; the card's own page is the only scroll.
 - **Multiplier in the model name** — model names show the credit multiplier in Trae's own menu format (e.g. `GLM-5.2 · x0.79`), updated with each directory refresh.

package/README.md

@@ -56,6 +56,7 @@
 - **文生图（`trae_draw_image`）** —— 把登录账号的 Trae 文生图能力接进会话：模型画一张图，插件把**图片字节一起取回来**、写进会话目录再显示给你。**默认关闭、按面板单独开**——生图真实消耗积分（实测 CN 个人版 `1920x1920` 一张约 8.8），所以它和识图那种「让不让看图」的开关不同，只能由你点头。协议、尺寸边界、取图那两步，以及为什么「取图」那条 GET 其实是又一次生成，见下方「[文生图](#文生图trae_draw_image)」。
 - **国内国际双区域自动识别** —— 自动发现 Trae CN / TRAE SOLO CN / Trae / TRAE SOLO 四个本地安装的登录账号；区域由凭证自带的 `userRegion` 声明自动判定（host 后缀与 edition 标签兜底），无需手动指定。**美国区（`userRegion: "US"` / `*.traeapi.us`）目前「识别但不接入」**：插件不会把 US 凭据当成新加坡区发出去，而会在账号面板明确写「美国区（US）暂不支持」并点名账号，同时说明重新登录不会改变结果（issue #66）。
 - **目录与勾选按面板隔离** —— 三个面板各一套模型目录、勾选、图片开关与上下文预算，各自读各自的槽位。名录从**该面板所钉的那条网关**读取——原本钉在企业池的客户端去读消费池名录，会永远发现不了自己池的独占模型。
+- **企业面板会列出租户自配的模型** —— 企业租户可以在 Trae 企业控制台配置自己的模型，这类行（`config_source: 2`）不在企业侧的 Remote 目录里，过去在插件里完全看不见，现在会出现在企业面板与 DSH 选择器里。**它们目前还调不通**：这批模型是客户端直连（`use_remote_service: false`、自带 `base_url`），插件没有对应传输通道，选中后调用会如实报错（`4001` → 该 SOLO function 不提供此模型），不会静默失败或假装成功。计费属租户池，所以**只在企业面板出现**，国内版与国际版不受影响——那两个面板本来也只读消费网关的名录。
 - **识图能力跟随 Trae 自身的标注** —— Trae 把某个模型标为 `multimodal` 时，插件直接按多模态对外声明，无需你在卡片上逐一手勾（issue #16）。判据是「**你手动勾选的 ∪ Trae 标注多模态的**」：Trae 明确标 `false` 或未标注的模型保持纯文本，你可以照旧手动为它们打开图片输入。卡片上被自动开启的那一行显示为已勾选且只读，并说明原因。详见下方「图片输入（识图）」。
 - **多账号切换** —— 支持重新读取 Token 列表并选择账号；Token 不写入 DSH 设置。**你的选择会被记住并长期生效**：插件不会因为某个账号额度用尽、或检测到另一个可用账号就自作主张替你切换（换账号意味着换人计费）——唯一的例外是你**亲自打开**的账号池（见下一条），那是一个显式选择，而不是插件的自作主张。所以当绑定的账号额度耗尽时，卡片会**明确告诉你**，并把本机其他还有额度的账号连同其可用积分数列出来，由你一键切换——而不是让面板一直空着、也不自动把你切走。「刷新账号与 Token」每次都会回报结果（找到几个账号、当前仍绑定谁），不会再「点了没反应」。下拉里显示的是产品名（`Trae` / `TRAE SOLO` / 国际版），便于分辨凭据来自哪个安装。
 - **账号导入 / 导出** —— 不用再为了用第二个账号而把凭据手工写进默认路径、顶掉上一个。在卡片账号区的「导入 / 导出账号」里：**导出**勾选若干账号下载一份 JSON；**导入**选择文件后先看**脱敏预览**（只显示账号标识与「是否有 Token」，不含凭据本身）再勾选导入。文件格式与同族 `dsh-connect-workbuddy` **互通**，两边导出的文件可以互相导入。导入按账号去重（同一账号再导入即覆盖更新），**认不出所属区域或因缺 Token 的记录会被跳过并计数**——国内版与国际版是两条并行计费通道，跨区导入会导致跨区计费，所以这里只认同能**正向识别**的区域（企业版共用 CN 凭据池，不构成第三条导入通道）。导出文件里是**有效 Token，请当作密码保管**。（issue #37）

package/lib/index.d.ts

@@ -462,14 +462,22 @@ interface TraeWireModel {
  *    account's custom models (`usage: 'custom_model'`); none of those belong
  *    in a model picker. Measured: this one test removed 23 of 50 wire-only
  *    rows, and every row it removed was a tool or a custom model.
- *  - `config_source === 1` — a Trae preset, not the account's own custom
- *    model (source 3, which carries the user's own base_url and key). The
- *    plugin must not offer to bill a model it does not host.
+ *  - `config_source === 1`, or `2` once the caller opts in — `1` is a Trae
+ *    preset; `2` is a model the tenant's own enterprise console configured
+ *    (see `allowTenantConfigured` on {@link mergeTraeModelSources}, which is
+ *    what decides whether a `2` may pass). `3` is the account's own custom
+ *    model, carrying the user's own base_url and key: the plugin must not
+ *    offer to bill a model it does not host, so `3` never passes.
  *  - a REAL display name — not empty, not the upstream placeholder `-`, not a
  *    bare config identifier (`search_agent_qwen_fast`,
  *    `computer_use_subagent`), and not the config's OWN id. A model with no
  *    name has nothing to show in the picker.
  *
+ *    A tenant-configured row (`2`) is EXEMPT from the "own id" clause: those
+ *    rows commonly publish the config_name as the display name, so the clause
+ *    would reject precisely the rows the opt-in exists to surface. The other
+ *    name tests still apply to them.
+ *
  * The display-name-collision test lives in the merge itself (it needs the
  * Remote rows to compare against); see {@link mergeTraeModelSources}. It is a
  * CAPABILITY test there, not a name test: a collision only suppresses a row
@@ -535,8 +543,19 @@ declare function isPromotableWireModel(model: TraeWireModel): boolean;
  * PROMOTED (issue #46) — subject to {@link isPromotableWireModel}. The
  * skeleton systematically omits the dated snapshot configs, so without
  * promotion every snapshot the IDE offers is unreachable from the plugin.
- */
-declare function mergeTraeModelSources(remote: readonly TraeDiscoveredModel[], wire: readonly TraeWireModel[]): TraeModelInfo[];
+ *
+ * @param options.allowTenantConfigured - may a `config_source: 2` row (a model
+ * the tenant's enterprise console configured) be promoted? Opt-in, and only
+ * the enterprise panel opts in: those rows bill the tenant pool, so surfacing
+ * them on a consumer panel would offer a model outside the caller's billing
+ * face. The rows also are not callable through `llm_utils_chat` today — they
+ * are client-direct with their own base_url (`use_remote_service: false`) and
+ * the gateway answers `4001` — which the discovery layer does not hide, but
+ * which is why this is a narrow opt-in rather than a default.
+ */
+declare function mergeTraeModelSources(remote: readonly TraeDiscoveredModel[], wire: readonly TraeWireModel[], options?: {
+  allowTenantConfigured?: boolean;
+}): TraeModelInfo[];
 /**
  * Demote a NON-chat `wireFunction` to "no function", keeping the row.
  *

package/lib/index.js

@@ -371,14 +371,22 @@ function applyImageSelection(models, selected) {
 *    account's custom models (`usage: 'custom_model'`); none of those belong
 *    in a model picker. Measured: this one test removed 23 of 50 wire-only
 *    rows, and every row it removed was a tool or a custom model.
-*  - `config_source === 1` — a Trae preset, not the account's own custom
-*    model (source 3, which carries the user's own base_url and key). The
-*    plugin must not offer to bill a model it does not host.
+*  - `config_source === 1`, or `2` once the caller opts in — `1` is a Trae
+*    preset; `2` is a model the tenant's own enterprise console configured
+*    (see `allowTenantConfigured` on {@link mergeTraeModelSources}, which is
+*    what decides whether a `2` may pass). `3` is the account's own custom
+*    model, carrying the user's own base_url and key: the plugin must not
+*    offer to bill a model it does not host, so `3` never passes.
 *  - a REAL display name — not empty, not the upstream placeholder `-`, not a
 *    bare config identifier (`search_agent_qwen_fast`,
 *    `computer_use_subagent`), and not the config's OWN id. A model with no
 *    name has nothing to show in the picker.
 *
+*    A tenant-configured row (`2`) is EXEMPT from the "own id" clause: those
+*    rows commonly publish the config_name as the display name, so the clause
+*    would reject precisely the rows the opt-in exists to surface. The other
+*    name tests still apply to them.
+*
 * The display-name-collision test lives in the merge itself (it needs the
 * Remote rows to compare against); see {@link mergeTraeModelSources}. It is a
 * CAPABILITY test there, not a name test: a collision only suppresses a row
@@ -391,9 +399,10 @@ function applyImageSelection(models, selected) {
 */
 function isPromotableWireModel(model) {
 	if (model.usage !== "chat_completion") return false;
-	if (model.configSource !== 1) return false;
+	if (model.configSource !== 1 && model.configSource !== 2) return false;
 	const name = model.name.trim();
 	if (name === "" || name === "-") return false;
+	if (model.configSource === 2) return true;
 	if (name === model.id.trim()) return false;
 	if (!name.includes(" ") && name.includes("_")) return false;
 	return true;
@@ -503,8 +512,17 @@ function wireEffortsOf(supported) {
 * PROMOTED (issue #46) — subject to {@link isPromotableWireModel}. The
 * skeleton systematically omits the dated snapshot configs, so without
 * promotion every snapshot the IDE offers is unreachable from the plugin.
+*
+* @param options.allowTenantConfigured - may a `config_source: 2` row (a model
+* the tenant's enterprise console configured) be promoted? Opt-in, and only
+* the enterprise panel opts in: those rows bill the tenant pool, so surfacing
+* them on a consumer panel would offer a model outside the caller's billing
+* face. The rows also are not callable through `llm_utils_chat` today — they
+* are client-direct with their own base_url (`use_remote_service: false`) and
+* the gateway answers `4001` — which the discovery layer does not hide, but
+* which is why this is a narrow opt-in rather than a default.
 */
-function mergeTraeModelSources(remote, wire) {
+function mergeTraeModelSources(remote, wire, options = {}) {
 	const wireByName = /* @__PURE__ */ new Map();
 	const wireById = /* @__PURE__ */ new Map();
 	for (const model of wire) if (!wireById.has(displayKey(model.id))) wireById.set(displayKey(model.id), model);
@@ -574,6 +592,7 @@ function mergeTraeModelSources(remote, wire) {
 	for (const model of remote) claim(model.name, model.contextWindow);
 	for (const wireModel of wire) {
 		if (remoteIds.has(displayKey(wireModel.id))) continue;
+		if (wireModel.configSource === 2 && options.allowTenantConfigured !== true) continue;
 		if (!isPromotableWireModel(wireModel)) continue;
 		const collides = claimedNames.has(displayKey(wireModel.name));
 		if (collides && (wireModel.contextWindow ?? 0) <= (claimedNames.get(displayKey(wireModel.name)) ?? 0)) continue;
@@ -1504,6 +1523,10 @@ const INERT_AUTH = {
 *
 * `imageOffloadCountQuantum` must be a positive integer no greater than
 * `maxRequestImages`; 10 ≤ 50 keeps the host's default ratio.
+*
+* The BYTE bound is the one field here that is not a host contract: it has to
+* match the gateway at the other end, and the gateways disagree (issue #81).
+* See {@link ENTERPRISE_MAX_REQUEST_IMAGE_BYTES}.
 */
 const REQUEST_IMAGE_BUDGETS = {
 	maxRequestImageBytes: 20971520,
@@ -1512,6 +1535,54 @@ const REQUEST_IMAGE_BUDGETS = {
 	maxRequestImages: 50,
 	imageOffloadCountQuantum: 10
 };
+/**
+* Request-image byte bound for the enterprise route, in bytes (8 MiB).
+*
+* WHY THE HOST DEFAULT IS WRONG HERE. `maxRequestImageBytes` is not a taste
+* setting — DSH compares it against the base64 aggregate of every image a
+* request re-inlines, and raising `IMAGE_OFFLOAD_REQUIRED` is how the oldest
+* images get replaced by placeholders and the request retried. That only works
+* if the bound is BELOW what the gateway accepts: a bound above it means the
+* host believes an unsendable request fits and sends it anyway.
+*
+* Measured 2026-11-09 with unauthenticated probes (openresty rejects on body
+* size before authentication, so no credentials or credits are involved):
+*
+*   console.enterprise.trae.cn, /api/agent/v3/create_agent_task AND
+*   /api/agent/v3/llm_utils_chat:
+*     10_485_758 bytes -> 401        10_485_762 bytes -> 413
+*     => the cap is exactly 10 MiB (10_485_760)
+*
+* The other two regions have no comparable cap: `trae-api-cn.mchost.guru`
+* answered 401 at 48 MiB and `coresg-normal.trae.ai` at 20 MiB, so they keep
+* the host default — lowering them would offload images those gateways accept.
+*
+* WHY 8 MiB AND NOT 10. The budget bounds the IMAGES; the request also carries
+* the system prompt, tool declarations and message text. 8 MiB leaves 2 MiB of
+* envelope, which the measured requests did not come close to (tool
+* declarations ~49 KB). The failure this fixes: a real 15-image session reached
+* 12.32 MB of base64 image payload, under the old 20 MiB budget and over the
+* 10 MiB cap, and died at step 20 with `413 Request Entity Too Large`.
+*/
+const ENTERPRISE_MAX_REQUEST_IMAGE_BYTES = 8388608;
+/**
+* Image-request budgets for one route.
+*
+* The byte bound is region-specific; every other field is shared. Kept as a
+* function rather than two constants so the shared fields cannot drift apart.
+*
+* The return type is the profile's own field types rather than
+* `typeof REQUEST_IMAGE_BUDGETS`: that constant is `as const`, so its
+* `maxRequestImageBytes` is the LITERAL `20_971_520` and the enterprise arm
+* would not typecheck against it.
+* @param providerId - the route whose gateway will receive the request.
+*/
+function requestImageBudgets(providerId) {
+	return providerId === "trae-enterprise" ? {
+		...REQUEST_IMAGE_BUDGETS,
+		maxRequestImageBytes: ENTERPRISE_MAX_REQUEST_IMAGE_BYTES
+	} : REQUEST_IMAGE_BUDGETS;
+}
 function toPiModel(info, baseUrl, providerId, withRate = true) {
 	return {
 		id: info.id,
@@ -1885,7 +1956,7 @@ function createTraeAdapter(options) {
 		configuredMaxTokens: /* @__PURE__ */ new Map(),
 		modelErrors: /* @__PURE__ */ new Map(),
 		defaultContextWindow: FALLBACK_CONTEXT_WINDOW,
-		...REQUEST_IMAGE_BUDGETS,
+		...requestImageBudgets(providerId),
 		piProvider: provider
 	};
 	let profiles = /* @__PURE__ */ new Map([[providerId, profile]]);
@@ -12127,7 +12198,7 @@ function apply(ctx, config) {
 			discoverModels: async (signal) => {
 				const remote = await withDirectoryRetry(() => remoteCatalog.fetchModels(signal));
 				const [wireModels, roster] = await Promise.all([solo.fetchModels(signal), officialRoster.fetch(signal)]);
-				const merged = mergeTraeModelSources(remote, wireModels);
+				const merged = mergeTraeModelSources(remote, wireModels, { allowTenantConfigured: panel === "enterprise" });
 				const callable = withChatCallableFunctions(merged, TRAE_DIRECTORY_FUNCTIONS[region]);
 				const chatFunctions = TRAE_DIRECTORY_FUNCTIONS[region];
 				for (const model of merged) {

package/package.json

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