dsh-connect-minimaxcode 0.5.3 → 0.5.5

package/README.en.md

@@ -79,6 +79,12 @@ dsh plugin --profile desktop add dsh-connect-minimaxcode
 
 For the Web profile, replace `--profile desktop` with `--profile web`.
 
+> **Installing a locally modified clone**: do not pass a directory path to `dsh plugin add` — pnpm installs it as a link and nests dependency symlinks inside the plugin's own `node_modules`; the host's plugin sandbox gets `EPERM` stat-ing those links and the plugin fails to activate (`failed to import`). Pack a tarball first, then install the tarball so dependencies resolve in the profile root `node_modules` like a registry install:
+
+```bash
+pnpm pack
+dsh plugin --profile desktop add ./dsh-connect-minimaxcode-0.5.5.tgz
+```
 > The desktop profile is owned exclusively by the Electron app. If the `dsh` command is not on your PATH, use the carrier CLI bundled with the DSH app (the path depends on the install location, for example `<DSH install dir>\resources\runtime\cli\bin\dsh.cmd`).
 
 After installing, the plugin hot-reloads, and the models then show up under the **MiniMax Code** group in the model picker.
@@ -297,10 +303,22 @@ The OAuth token is valid for about an hour and is refreshed automatically by the
 - **No settings card is provided**. The plugin does not register a card on the DSH settings page; the interface it adds is a single pill in the composer tool row (**drawn only while this plugin's model is selected**) and a small card on the plugin page.
 - **The upstream APIs are non-public** and may stop working when MiniMax updates its client. If the balance API breaks, the pill shows "credits unavailable", which does not affect model traffic.
 - **Image input depends on the host's attachment service.** The catalog declares the `image` modality (`M3`, `M3.1-Flash`), but turning a durable attachment into request bytes is the host's job: without that service the plugin still loads and serves text, and only image requests are refused.
+- **The context window is declared as the gateway's real ceiling (1,000,000), not the 512,000 in the catalog.** Upstream's `limit.context` is the *default* window and the billing tier boundary (input above 512k costs more); the largest entry of `context_window_options` is the ceiling the gateway enforces. Measured on 2026-10-25: 946,206 tokens were served normally, 1,050,000 were refused (`invalid params, context window exceeds limit (2013)`). Declaring 512,000 meant every turn of a long conversation was reported as `pi-ai detected context overflow` — while the model had answered perfectly well and the reply was thrown away.
 - **The device code flow needs `account.minimax.cn` to be reachable**, and the browser that authorizes it has to be able to sign in to a MiniMax account. On some restricted networks the authorization page cannot be opened.
 
 ## Changelog
 
+### 0.5.5 (2026-11-06)
+
+- **New "rate-limit windows" readout**: reads the open platform's `GET /backend/account/token_plan/remains_percent` (found in the desktop app's own traffic, likewise undocumented) and shows the plan's **5-hour window** and **weekly window** with used percentages and a reset countdown. Window lengths are derived from the response's own edges, never hard-coded.
+- The endpoint belongs to the account domain and **accepts only the OAuth token** (desktop app or plugin sign-in); a JWT answers `1016 invalid api key`. The read rides the credits poller with independent failure handling.
+- Shown in the pill detail and the plugin page card; `tests/rate-limit.spec.ts` pins parsing, URL, failure handling and the polling wiring.
+### 0.5.4 (2026-10-29)
+
+- **Fixed long conversations being reported as context overflow**: upstream's `limit.context` (512,000) is the *default* window and the billing tier boundary, while the ceiling the gateway enforces is the 1,000,000 in `context_window_options`. Declaring 512,000 meant that once a conversation crossed that line, *every* turn was reported as `pi-ai detected context overflow` — even though the model answered normally and the reply was discarded. The window is now declared as the ceiling the gateway actually enforces.
+- The built-in fallback roster (used when the catalog cannot be fetched) now declares 1,000,000 as well.
+- Four new cases pin the window parsing: the largest of `context_window_options` wins, upstream's `limit.context` is the fallback, a malformed option list is ignored, and the fallback roster does not claim 512k.
+
 ### 0.5.3 (2026-10-25)
 
 - **Fixed image input**: an upload used to fail every time — `pi-ai image input requires the durable attachment service` (`UNSUPPORTED_CONTENT`). The catalog always declared `image` among a model's input modalities, but the plugin built its `PiAiAdapter` without `resolveAttachments` or `resolveImageAccess`, so pi-ai had no way to turn a durable attachment reference into request bytes and refused the call before it reached the gateway. The plugin now reads the host's `attachments` service on demand and maps an attachment's host path into the current execution world with `fs.processPathFromHostPath`; a host that offers no attachment service gets `undefined` for both hooks, and text-only calls are unchanged.
@@ -455,6 +473,8 @@ dsh plugin --profile web exec dsh-workbuddy-connect status
 ## Contributors
 
 - **[eghrhegpe](https://github.com/eghrhegpe)** — raised the request for a plugin-page icon and Chinese/English copy ([#1](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/issues/1)). It became 0.5.2: the plugin page has its own SVG artwork, the title and the introduction come in both languages, and the interface follows the host's language.
+- **[azsora](https://github.com/azsora)** — found the plan's rate-limit endpoint in the desktop app's own traffic and wired the 5-hour and weekly usage windows into the credit pill and the plugin page ([#4](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/4)): the window length is derived from the response's own edges rather than hard-coded. It became 0.5.5.
+- **[qzz19970504](https://github.com/qzz19970504)** — found and fixed the wiring gap that made every image upload fail ([#3](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/3)): the catalog declared the `image` modality, but the adapter never connected the host's durable attachment service, so pi-ai refused image requests before they were sent. The fix became 0.5.3.
 - Plugin author: **[JeffTsuiCUG](https://github.com/JeffTsuiCUG)**
 
 ## Acknowledgements

package/README.md

@@ -85,6 +85,12 @@ dsh plugin --profile desktop add dsh-connect-minimaxcode
 
 Web profile 把 `--profile desktop` 换成 `--profile web`。
 
+> **本地开发装自己改过的克隆**：不要把目录路径直接传给 `dsh plugin add`——pnpm 会以链接方式安装，把依赖的软链嵌进插件自己的 `node_modules`，宿主的插件沙箱 `stat` 这些链接会得到 `EPERM`，插件激活失败（`failed to import`）。先 `pnpm pack` 打成 tarball，再安装 tarball，依赖就会像 registry 安装一样解析在 profile 根 `node_modules`：
+
+```bash
+pnpm pack
+dsh plugin --profile desktop add ./dsh-connect-minimaxcode-0.5.5.tgz
+```
 > 桌面版的 profile 由 Electron 应用独占，若 `dsh` 命令不在 PATH 中，请使用 DSH 应用自带的载体 CLI（路径随安装位置而变，例如 `<DSH安装目录>\resources\runtime\cli\bin\dsh.cmd`）。
 
 安装后插件会热加载，模型随后出现在模型选择器的 **MiniMax Code** 分组中。
@@ -283,6 +289,32 @@ GET https://agent.minimax.cn/minimax-cloud/api/v1/credit/details?page_number=1&p
 
   > 官方价目表没有单列**缓存写入**（`cache_creation_input_tokens`）的单价，因此插件只统计它的 token 数、**不折算金额**，以免给出一个没有公开依据的数字。
 
+### 限额窗口（套餐的两个滚动窗口）
+
+套餐用量按两个滚动窗口计量（当前套餐为 5 小时与 7 天），插件会显示各窗口的已用百分比与重置倒计时：
+
+```
+GET https://www.minimaxi.com/backend/account/token_plan/remains_percent?business=Agent&device_platform=desktop
+Authorization: Bearer <OAuth 令牌>
+```
+
+```json
+"model_remains": [{
+  "model_name": "general",
+  "start_time": 1793882204091, "end_time": 1793900204091,   // 差值 = 5 小时
+  "current_interval_used_percent": "19%",
+  "weekly_start_time": 1793783898054, "weekly_end_time": 1794388698054,  // 差值 = 7 天
+  "current_weekly_used_percent": "29%"
+}]
+```
+
+几点实测结论：
+
+- **窗口时长不写死**：从响应自身的起止字段推导（实测恰为 5 小时与 7 天），套餐条款变了显示会跟着变 —— 胶囊与详情行上的窗口名（`5h`、`7d`）也是这么来的，不是写死的字面量
+- **无限量的窗口不报百分比**：上游用 `current_*_status` 标出没有额度的窗口（桌面 App 读作 `isUnlimited: 3 === status`），这类窗口不参与显示，避免出现「0%」这种没人能据此行动的读数
+- **该接口在开放平台域**（`www.minimaxi.com`），只认 OAuth 令牌；JWT 打它返回 `1016 invalid api key`
+- **接口异常时其余显示不受影响**：限额读不到，胶囊与卡片仍显示余额、签到与本机用量
+- 上游还发 `current_*_count` 计数字段（无计数制时为 `-1`），插件只读百分比与起止时刻
 ### 关于续期
 
 OAuth 令牌有效期约 1 小时，由客户端自动续期。插件**只在自己的令牌已过期时**才用 App 已存的 refresh token 续一次，并把轮换后的新令牌按客户端**原格式原子写回**同一个文件（`generation` 保持不变），因此桌面 App 的登录态不受影响。插件不会发起登录、不会登出、也不会调用任何付费/订阅类接口。
@@ -303,10 +335,24 @@ OAuth 令牌有效期约 1 小时，由客户端自动续期。插件**只在自
 - **不提供设置界面卡片**。插件不在 DSH 设置页注册卡片；界面只在输入框工具行增加一枚胶囊（**仅选中本插件的模型时显示**），以及插件页面里的一张小卡片。
 - **上游接口非公开**，MiniMax 客户端更新后可能失效。余额接口失效时胶囊会显示「积分不可用」，不会影响模型对话。
 - **发图依赖宿主的附件服务**。模型目录声明了 `image` 模态（`M3`、`M3.1-Flash`），但把持久化附件读成请求字节是宿主的活儿：宿主没有附件服务时插件仍能加载并服务文本，只是带图的请求会被拒绝。
+- **上下文窗口按网关的真实上限声明（1,000,000），不是目录里的 512,000**。上游 `limit.context` 是**默认档位与计费分界**（输入超过 512k 的部分按更高倍率计费），`context_window_options` 里最大的一档才是网关执行的硬上限。实测（2026-10-25）：946,206 tokens 正常受理，1,050,000 被拒（`invalid params, context window exceeds limit (2013)`）。此前按 512,000 声明，长会话一旦过线就**每一轮**都被判成「上下文溢出」，模型其实答得好好的，回复却被丢掉（`pi-ai detected context overflow`）。
 - **设备码流需要能访问 `account.minimax.cn`**，且授权时要在浏览器里能登录 MiniMax 账号。某些内网或受限网络下打不开授权页。
 
 ## 更新记录
 
+### 0.5.5（2026-11-07）
+
+- **新增「限额窗口」显示**：读取开放平台的 `GET /backend/account/token_plan/remains_percent`（该接口来自桌面 App 每天真实调用的日志，同样未在官方文档中公开），展示套餐的**5 小时窗口**与**每周窗口**的已用百分比与重置倒计时。窗口时长从响应自身的起止字段推导，不写死 5 小时或 7 天——套餐条款变过不止一次，显示应跟随服务端所说。
+- 该接口属于账户域，**只认 OAuth 令牌**（桌面 App 登录态或插件自登录均可）；JWT 打它返回 `1016 invalid api key`。读取挂在积分轮询上，独立容错：限额读不到不影响余额显示，反之亦然。
+- 显示位置：胶囊详情与插件页卡片各两行；新增 `tests/rate-limit.spec.ts` 钉住解析、URL、容错与轮询接线。
+- 窗口名跟随服务端：胶囊主标签与详情行上的窗口长度（`5h`、`7d`）从响应的起止字段推导，而不是写死 —— 解析层早已「不写死窗口长度」，显示层此前却写着「5h」，两处现在一致。
+- 无限量窗口不报百分比：上游用 `current_*_status` 标出没有额度的窗口，这类窗口不参与显示，避免出现没人能据此行动的「0%」。
+### 0.5.4（2026-10-29）
+
+- **修复长会话被误判为「上下文溢出」**：上游 `limit.context`（512,000）是**默认档位与计费分界**，网关实际执行的上限是 `context_window_options` 里的 1,000,000。此前按 512,000 声明，会话一旦超过这条线，**每一轮**都会被判定为 `pi-ai detected context overflow` —— 而模型其实正常答了，回复却被丢弃。现在按网关的真实上限声明窗口。
+- 兜底名录（离线时的内置猜测）同步改为 1,000,000。
+- 新增 4 个用例钉住窗口解析：取 `context_window_options` 的最大值、上游没给就回落 `limit.context`、非法列表被忽略、兜底名录的窗口不是 512k。
+
 ### 0.5.3（2026-10-25）
 
 - **修复图片输入**：此前发图必然失败 —— `本轮运行失败 pi-ai image input requires the durable attachment service`（`UNSUPPORTED_CONTENT`）。模型目录一直把 `image` 写进模型的输入模态，但插件构造 `PiAiAdapter` 时没有给 `resolveAttachments` 与 `resolveImageAccess` 两个钩子，pi-ai 因此无法把持久化的附件引用变成请求字节，在发往网关之前就拒绝了调用。现在插件按需读取宿主的 `attachments` 服务，并用 `fs.processPathFromHostPath` 把附件的宿主路径映射进当前执行世界；宿主没有提供附件服务时这两个钩子为 `undefined`，纯文本调用不受影响。
@@ -461,6 +507,8 @@ dsh plugin --profile web exec dsh-workbuddy-connect status
 ## 贡献者
 
 - **[eghrhegpe](https://github.com/eghrhegpe)** —— 提出了插件页图标与中英文文案的建议（[#1](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/issues/1)）。这条建议促成了 0.5.2：插件页有了自己的 SVG 图标，标题与简介有了中英两版，界面文案也开始跟随宿主语言。
+- **[azsora](https://github.com/azsora)** —— 从桌面 App 的实际调用里找出了套餐的**限额窗口接口**，并把 5 小时与每周两个窗口的用量接进了积分胶囊与插件页卡片（[#4](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/4)）：窗口时长从响应自身的起止字段推导，不写死。该功能成为 0.5.5。
+- **[qzz19970504](https://github.com/qzz19970504)** —— 定位并修复了「发图必然失败」的接线缺口（[#3](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/3)）：模型目录声明了 `image` 模态，但适配器没有把宿主的持久化附件服务接上，导致带图请求被 pi-ai 在发出前拒掉。该修复成为 0.5.3。
 - 插件作者：**[JeffTsuiCUG](https://github.com/JeffTsuiCUG)**
 
 ## 致谢

package/lib/client.js

@@ -66,6 +66,8 @@
         signinAuto: '每天自动签到',
         signinClaim: '签到',
         claimableToday: '今日可签到',
+        usageWindow: '{duration}限额',
+        resetIn: '{duration}后',
     };
     const en = {
         title: 'MiniMax Code credits',
@@ -106,6 +108,8 @@
         signinAuto: 'Claim daily on its own',
         signinClaim: 'Claim',
         claimableToday: 'Claimable today',
+        usageWindow: '{duration} limit',
+        resetIn: 'resets in {duration}',
     };
     const loader = globalThis.__ModuleLoader__;
     if (loader === undefined)
@@ -208,6 +212,53 @@
                     ? row(t('expiringSoon', { amount: credits(credits_.expiringSoon, 2) }), '')
                     : null, next !== undefined ? row(t('nextExpiry'), day(next)) : null);
             }
+            /**
+             * A countdown to a window reset, coarse on purpose: minutes below an
+             * hour, hours and minutes below a day, days and hours beyond. It is
+             * computed at render time, so it is as fresh as the last status read.
+             */
+            function countdown(resetAtMs) {
+                const minutes = Math.max(0, Math.ceil((resetAtMs - Date.now()) / 60000));
+                if (minutes < 60)
+                    return `${minutes}m`;
+                if (minutes < 1440)
+                    return `${Math.floor(minutes / 60)}h${minutes % 60}m`;
+                return `${Math.floor(minutes / 1440)}d${Math.floor((minutes % 1440) / 60)}h`;
+            }
+            /**
+             * The length of a window, as the server defines it.
+             *
+             * The window's own edges give the length, so the label follows the plan
+             * instead of the plan's terms today: five hours today reads "5h", and a
+             * plan that moved to a three-hour window reads "3h" without a code
+             * change. Only the word around it is translated.
+             */
+            function windowLabel(window) {
+                const minutes = Math.max(1, Math.round((window.resetAtMs - window.startAtMs) / 60000));
+                if (minutes >= 1440)
+                    return `${Math.round(minutes / 1440)}d`;
+                if (minutes >= 60) {
+                    const hours = minutes / 60;
+                    return Number.isInteger(hours) ? `${hours}h` : `${Math.floor(hours)}h${minutes % 60}m`;
+                }
+                return `${minutes}m`;
+            }
+            /**
+             * The plan's two rolling usage windows, shared by the pill's detail and
+             * the page card.
+             *
+             * The percent sits on the right with the reset countdown in
+             * parentheses, and the window length is derived from the window itself
+             * rather than written into the label: the plan's terms have changed
+             * before, and the display should follow whatever the server says.
+             */
+            function rateLimitBlock(t, rateLimit) {
+                if (rateLimit === undefined || rateLimit.state !== 'ok')
+                    return null;
+                if (rateLimit.interval === undefined || rateLimit.weekly === undefined)
+                    return null;
+                return h('div', { style: expiryBoxStyle, 'data-minimax-rate-limit': true }, row(t('usageWindow', { duration: windowLabel(rateLimit.interval) }), `${rateLimit.interval.usedPercent}%(${t('resetIn', { duration: countdown(rateLimit.interval.resetAtMs) })})`), row(t('usageWindow', { duration: windowLabel(rateLimit.weekly) }), `${rateLimit.weekly.usedPercent}%(${t('resetIn', { duration: countdown(rateLimit.weekly.resetAtMs) })})`));
+            }
             /** The pill itself; the gate decides whether it is drawn at all. */
             function CreditPill(props) {
                 const [status] = useStatus();
@@ -218,14 +269,29 @@
                 });
                 const credits_ = status?.credits;
                 const usage = status?.usage;
+                const rateLimit = status?.rateLimit;
                 const available = credits_?.state === 'ok' && credits_.total !== undefined;
-                const label = available
+                const windows = rateLimit?.state === 'ok' && rateLimit.interval !== undefined && rateLimit.weekly !== undefined
+                    ? { interval: rateLimit.interval, weekly: rateLimit.weekly }
+                    : undefined;
+                // A window that is used up means the plan cannot serve the next
+                // request right now, so the balance is the number worth seeing.
+                // Otherwise the pill leads with the short window — the one that gates
+                // the next request — named by the length the server gives it. No
+                // windows, the balance again: the pill never shows nothing just
+                // because one read failed.
+                const exhausted = windows !== undefined
+                    && (windows.interval.usedPercent >= 100 || windows.weekly.usedPercent >= 100);
+                const balance = available
                     ? t('balance', { total: credits(credits_.total, 2) })
                     : t(credits_?.state === 'expired' ? 'expired' : credits_?.state === 'signed-out' ? 'signedOut' : 'unavailable');
+                const label = windows === undefined || exhausted
+                    ? balance
+                    : `${windowLabel(windows.interval)}  ${windows.interval.usedPercent}%(${t('resetIn', { duration: countdown(windows.interval.resetAtMs) })})`;
                 const detail = available
                     ? h('div', { style: detailStyle, 'data-minimax-credits-detail': true }, row(t('free'), credits(credits_.free, 3)), row(t('purchased'), credits(credits_.purchased, 3)), credits_.consumed !== undefined && credits_.consumed > 0
                         ? row(t('consumed'), credits(credits_.consumed, 3))
-                        : null, expiryBlock(t, credits_), usage !== undefined
+                        : null, expiryBlock(t, credits_), rateLimitBlock(t, status?.rateLimit), usage !== undefined
                         ? h('div', { style: rowStyle }, h('span', null, t('tokens', { count: tokens(usage.inputTokens + usage.outputTokens + usage.cacheReadTokens) })), h('span', null, t('cost', { amount: money(usage.estimatedCny) })))
                         : null, credits_.updatedAtMs !== undefined
                         ? row(t('updated', { time: new Date(credits_.updatedAtMs).toLocaleTimeString() }), '')
@@ -366,7 +432,7 @@
                 if (!available) {
                     return h('div', { style: cardStyle, 'data-minimax-credits-card': true }, h('div', { style: cardTitleStyle }, t('title')), h('div', { style: rowStyle }, h('span', null, t('unavailable')), h('span', null, credits_?.state === 'expired' ? t('expired') : '')), loginBlock(t, login, refresh));
                 }
-                return h('div', { style: cardStyle, 'data-minimax-credits-card': true }, h('div', { style: cardTitleStyle }, t('title')), h('div', { style: bigNumberStyle }, t('balance', { total: credits(credits_.total, 2) })), row(t('free'), credits(credits_.free, 3)), row(t('purchased'), credits(credits_.purchased, 3)), expiryBlock(t, credits_), signinBlock(t, signin, refresh), h('div', { style: sectionTitleStyle }, t('lots')), (credits_.upcoming ?? []).length === 0
+                return h('div', { style: cardStyle, 'data-minimax-credits-card': true }, h('div', { style: cardTitleStyle }, t('title')), h('div', { style: bigNumberStyle }, t('balance', { total: credits(credits_.total, 2) })), row(t('free'), credits(credits_.free, 3)), row(t('purchased'), credits(credits_.purchased, 3)), expiryBlock(t, credits_), rateLimitBlock(t, status?.rateLimit), signinBlock(t, signin, refresh), h('div', { style: sectionTitleStyle }, t('lots')), (credits_.upcoming ?? []).length === 0
                     ? h('div', { style: mutedStyle }, t('noLots'))
                     : h('ul', { style: listStyle }, ...(credits_.upcoming ?? []).map((lot, index) => h('li', { key: `${lot.expireAtMs}-${index}`, style: rowStyle }, h('span', null, day(lot.expireAtMs)), h('span', null, credits(lot.amount, 2))))), usage !== undefined
                     ? h('div', { style: usageBoxStyle }, row(t('tokens', { count: tokens(usage.inputTokens + usage.outputTokens + usage.cacheReadTokens) }), ''), row(t('cost', { amount: money(usage.estimatedCny) }), ''), usage.requests > 0 ? row(t('requests', { count: usage.requests }), usage.lastModel ?? '') : null)

package/lib/index.d.ts

@@ -145,6 +145,11 @@ declare const MINIMAXCODE_PROVIDER_ID = "minimaxcode";
  * when upstream retired `MiniMax-M2.7` and `MiniMax-M2.7-highspeed` and
  * promoted the model previously served anonymously (internally "space bunny")
  * as `MiniMax-M3.1-Flash`.
+ *
+ * The window is 1,000,000 rather than the 512,000 the upstream `limit` block
+ * reports: 512k is the billing tier boundary, and the gateway itself was
+ * measured serving 946,206 tokens before refusing ~1,050,000 with
+ * `invalid params, context window exceeds limit (2013)`.
  */
 declare const FALLBACK_MODELS: readonly CatalogModel[];
 /** Where the currently served list came from. */
@@ -203,6 +208,8 @@ declare class MinimaxCatalog {
 declare const MINIMAX_OAUTH_CLIENT_ID = "mcode-public";
 /** Membership endpoint: carries the credit summary. */
 declare const MEMBERSHIP_PATH = "/matrix/api/v1/commerce/get_membership_info";
+/** Rate-limit window endpoint: the 5-hour and weekly usage the plan meters. */
+declare const REMAINS_PERCENT_PATH = "/backend/account/token_plan/remains_percent";
 /** The OAuth credential the account endpoints accept. */
 interface OAuthCredential {
   /** The `mmoat_` bearer token. */
@@ -331,6 +338,48 @@ interface CreditLot {
   /** The upstream's kind of lot, when it says. */
   creditType?: number;
 }
+/** One metered window: a span of time and how much of its allowance went. */
+interface UsageWindow {
+  /** The share of the window's allowance already used, in percent. */
+  usedPercent: number;
+  /** When the window opened, in milliseconds since the epoch. */
+  startAtMs: number;
+  /** When the window closes and the allowance resets, in milliseconds since the epoch. */
+  resetAtMs: number;
+}
+/** The two rolling windows the plan meters usage in. */
+interface RateLimitWindows {
+  /** The short window (five hours on the plans seen so far). */
+  interval: UsageWindow;
+  /** The weekly window (seven days on the plans seen so far). */
+  weekly: UsageWindow;
+}
+/**
+ * Read the two rate-limit windows out of a remains-percent response.
+ *
+ * The upstream answers with one entry per metered group; the general one is
+ * the only one the plan meters today, and the first entry is used when it is
+ * absent. The percents arrive as strings ("19%"), and the counts arrive as -1
+ * when the plan does not meter by count, so only the percents and the window
+ * edges are read. The window length is derived from the entry's own endpoints
+ * rather than assumed to be five hours or seven days — the plan's terms have
+ * changed before, and the display should follow whatever the server says.
+ *
+ * A window the server marks as unlimited (`current_*_status` of 3) carries no
+ * allowance to be a percentage of, so it produces no window at all: reporting
+ * "0%" of an unlimited quota would be a number nobody can act on.
+ */
+declare function parseRateLimitWindows(document: unknown): RateLimitWindows | undefined;
+/**
+ * Fetch the plan's two rate-limit windows.
+ *
+ * The endpoint lives on the open-platform host, like the usage summary, and
+ * answers the same OAuth credential the membership endpoint takes. The JWT the
+ * model gateway accepts does not work here: this is an account endpoint.
+ *
+ * @returns The windows, or `undefined` when the response carries none.
+ */
+declare function fetchRateLimitWindows(credential: OAuthCredential, region: MinimaxRegion, fetchImpl?: typeof fetch): Promise<RateLimitWindows | undefined>;
 /** What the lots say about credits that are about to be lost. */
 interface ExpirySummary {
   /** Credits in lots that expire within {@link EXPIRING_WINDOW_DAYS} days. */
@@ -369,12 +418,20 @@ declare class MinimaxCredits {
   get ledgerAtMs(): number | undefined;
   /** Why the ledger could not be read, when it could not. */
   get ledgerError(): string | undefined;
+  /** The plan's rate-limit windows as last read. */
+  get rateLimit(): RateLimitWindows | undefined;
+  /** Why the windows could not be read, when they could not. */
+  get rateLimitError(): string | undefined;
+  /** When the windows were last read. */
+  get rateLimitAtMs(): number | undefined;
   /**
    * Read the balance and record how much was consumed since the last read.
    *
    * The credit ledger is read alongside it, but a ledger that cannot be read
    * never hides the balance: the two come from different endpoints and only
-   * the balance is essential.
+   * the balance is essential. The rate-limit windows ride along under the
+   * same rule — they come from yet another endpoint, and none of the three
+   * takes the others down with it.
    *
    * @returns Whether the balance changed.
    */
@@ -387,6 +444,13 @@ declare class MinimaxCredits {
    * take it down with it.
    */
   refreshLedger(credential: OAuthCredential, region: MinimaxRegion, fetchImpl?: typeof fetch, now?: number): Promise<void>;
+  /**
+   * Read the plan's rate-limit windows.
+   *
+   * Same rule as the ledger: a failure is remembered but never thrown, and a
+   * window that cannot be read leaves the last one on display.
+   */
+  refreshRateLimit(credential: OAuthCredential, region: MinimaxRegion, fetchImpl?: typeof fetch, now?: number): Promise<void>;
 }
 //#endregion
 //#region src/usage.d.ts
@@ -826,6 +890,27 @@ interface UsageStatus {
   /** How many requests were measured. */
   requests: number;
 }
+/** The plan's two rolling usage windows, as the card reads them. */
+interface RateLimitStatus {
+  /** Whether the windows could be read. */
+  state: 'ok' | 'unavailable' | 'expired' | 'signed-out';
+  /** The short window (five hours on the plans seen so far). */
+  interval?: {
+    usedPercent: number;
+    startAtMs: number;
+    resetAtMs: number;
+  };
+  /** The weekly window. */
+  weekly?: {
+    usedPercent: number;
+    startAtMs: number;
+    resetAtMs: number;
+  };
+  /** When the windows were read, in milliseconds since the epoch. */
+  updatedAtMs?: number;
+  /** Why the windows could not be read. */
+  error?: string;
+}
 /** What the card renders. */
 interface StatusDocument {
   state: 'signed-in' | 'signed-out' | 'expired';
@@ -848,6 +933,8 @@ interface StatusDocument {
   refreshing?: boolean;
   /** The account's credit balance, when it could be read. */
   credits?: CreditStatus;
+  /** The plan's rolling usage windows, when they could be read. */
+  rateLimit?: RateLimitStatus;
   /** What this host's requests have used. */
   usage?: UsageStatus;
   /** The daily check-in, when it could be read. */
@@ -874,6 +961,8 @@ interface StatusDeps {
   refreshing: boolean;
   /** The account's credit balance, when the account API could be reached. */
   credits?: CreditStatus;
+  /** The plan's rolling usage windows, when the open platform could be reached. */
+  rateLimit?: RateLimitStatus;
   /** What this host's requests have used. */
   usage?: UsageStatus;
   /** The daily check-in, when the account API could be reached. */
@@ -963,4 +1052,4 @@ declare const inject: string[];
  */
 declare function apply(ctx: Context): void;
 //#endregion
-export { type AuthState, type CatalogModel, type CatalogSource, type Credential, type CreditSummary, DEVICE_CODE_GRANT, DEVICE_CODE_PATH, type DeviceLoginState, EMPTY_USAGE, FALLBACK_MODELS, MEMBERSHIP_PATH, MINIMAXCODE_PROVIDER_ID, MINIMAX_ACTION_PATH, MINIMAX_AUTH_FILENAME, MINIMAX_DATA_DIR, MINIMAX_GATEWAYS, MINIMAX_OAUTH_CLIENT_ID, MINIMAX_REGIONS, MINIMAX_STATUS_PATH, MINIMAX_STREAM_IDLE_TIMEOUT_MS, MODEL_PRICES, MinimaxCatalog, MinimaxCredits, type MinimaxRegion, type ModelUsage, type OAuthCredential, type OAuthState, PLUGIN_CREDENTIAL_FILENAME, PLUGIN_STATE_FILENAME, type PluginCredential, type PluginState, SIGNIN_CLAIM_PATH, SIGNIN_CLAIM_RESULT, SIGNIN_CYCLE_DAYS, SIGNIN_DAY_STATUS, SIGNIN_PANEL_PATH, type SigninClaim, type SigninDay, type SigninPanel, type StatusDocument, type TokenClaims, UsageMeter, apply, authPath, bearerToken, catalogUrl, chatBaseUrl, claimSignin, createMinimaxCodeAdapter, dataDir, daysRemaining, decodeClaims, dshHome, ensureOAuthCredential, estimateCny, expiresInMs, expiryLevel, fetchCreditSummary, fetchSigninPanel, inject, localDay, makePkce, name, parseAuthDocument, parseCatalog, parseCreditSummary, parseOAuthDocument, parseSigninClaim, parseSigninPanel, pluginCredentialPath, pluginStatePath, pollDeviceLogin, priceFor, readCredential, readOAuthCredential, readPluginCredential, readPluginState, refreshOAuthCredential, refreshPluginCredential, startDeviceLogin, statusDocument, timezoneId, writeOAuthCredential, writePluginCredential, writePluginState };
+export { type AuthState, type CatalogModel, type CatalogSource, type Credential, type CreditSummary, DEVICE_CODE_GRANT, DEVICE_CODE_PATH, type DeviceLoginState, EMPTY_USAGE, FALLBACK_MODELS, MEMBERSHIP_PATH, MINIMAXCODE_PROVIDER_ID, MINIMAX_ACTION_PATH, MINIMAX_AUTH_FILENAME, MINIMAX_DATA_DIR, MINIMAX_GATEWAYS, MINIMAX_OAUTH_CLIENT_ID, MINIMAX_REGIONS, MINIMAX_STATUS_PATH, MINIMAX_STREAM_IDLE_TIMEOUT_MS, MODEL_PRICES, MinimaxCatalog, MinimaxCredits, type MinimaxRegion, type ModelUsage, type OAuthCredential, type OAuthState, PLUGIN_CREDENTIAL_FILENAME, PLUGIN_STATE_FILENAME, type PluginCredential, type PluginState, REMAINS_PERCENT_PATH, type RateLimitWindows, SIGNIN_CLAIM_PATH, SIGNIN_CLAIM_RESULT, SIGNIN_CYCLE_DAYS, SIGNIN_DAY_STATUS, SIGNIN_PANEL_PATH, type SigninClaim, type SigninDay, type SigninPanel, type StatusDocument, type TokenClaims, UsageMeter, apply, authPath, bearerToken, catalogUrl, chatBaseUrl, claimSignin, createMinimaxCodeAdapter, dataDir, daysRemaining, decodeClaims, dshHome, ensureOAuthCredential, estimateCny, expiresInMs, expiryLevel, fetchCreditSummary, fetchRateLimitWindows, fetchSigninPanel, inject, localDay, makePkce, name, parseAuthDocument, parseCatalog, parseCreditSummary, parseOAuthDocument, parseRateLimitWindows, parseSigninClaim, parseSigninPanel, pluginCredentialPath, pluginStatePath, pollDeviceLogin, priceFor, readCredential, readOAuthCredential, readPluginCredential, readPluginState, refreshOAuthCredential, refreshPluginCredential, startDeviceLogin, statusDocument, timezoneId, writeOAuthCredential, writePluginCredential, writePluginState };

package/lib/index.js

@@ -238,11 +238,16 @@ const MINIMAXCODE_PROVIDER_ID = "minimaxcode";
 * when upstream retired `MiniMax-M2.7` and `MiniMax-M2.7-highspeed` and
 * promoted the model previously served anonymously (internally "space bunny")
 * as `MiniMax-M3.1-Flash`.
+*
+* The window is 1,000,000 rather than the 512,000 the upstream `limit` block
+* reports: 512k is the billing tier boundary, and the gateway itself was
+* measured serving 946,206 tokens before refusing ~1,050,000 with
+* `invalid params, context window exceeds limit (2013)`.
 */
 const FALLBACK_MODELS = [{
 	id: "MiniMax-M3",
 	name: "M3",
-	contextWindow: 512e3,
+	contextWindow: 1e6,
 	maxOutputTokens: 128e3,
 	toolCall: true,
 	reasoning: true,
@@ -255,7 +260,7 @@ const FALLBACK_MODELS = [{
 }, {
 	id: "MiniMax-M3.1-Flash",
 	name: "M3.1-Flash",
-	contextWindow: 512e3,
+	contextWindow: 1e6,
 	maxOutputTokens: 128e3,
 	toolCall: true,
 	reasoning: true,
@@ -278,12 +283,42 @@ function sameCatalog(a, b) {
 function usable(id, raw) {
 	return id.length > 0 && id.startsWith("MiniMax-") && typeof raw === "object" && raw !== null;
 }
+/**
+* The window the gateway actually enforces.
+*
+* Upstream reports two different numbers, and they mean different things:
+* `limit.context` is the *default* window — the billing tier boundary, above
+* which input costs more — while `context_window_options` lists every window
+* the gateway will accept, the largest being the hard ceiling.
+*
+* Measured against the live gateway on 2026-10-25: a prompt of 946,206 tokens
+* was served normally, and one of ~1,050,000 was refused with
+* `invalid params, context window exceeds limit (2013)`. The ceiling is
+* therefore the largest option, not `limit.context`.
+*
+* Declaring the default instead of the ceiling is not a cosmetic difference:
+* the adapter compares the gateway's own token count against this number, so a
+* conversation that runs past 512k is reported as a context overflow on every
+* turn even though the gateway answers it perfectly well.
+*
+* @param raw - The upstream model entry.
+* @param limit - The upstream `limit` block, already read.
+* @returns The window to declare, in tokens.
+*/
+function readContextWindow(raw, limit) {
+	const options = raw.context_window_options;
+	if (Array.isArray(options)) {
+		const sizes = options.filter((value) => typeof value === "number" && Number.isInteger(value) && value > 0);
+		if (sizes.length > 0) return Math.max(...sizes);
+	}
+	return typeof limit.context === "number" ? limit.context : 2e5;
+}
 /** Read the fields the upstream sends, tolerating their absence. */
 function readModel(id, raw) {
 	const limit = raw.limit ?? {};
 	const modalities = raw.modalities ?? {};
 	const input = Array.isArray(modalities.input) ? modalities.input.filter((m) => typeof m === "string") : ["text"];
-	const contextWindow = typeof limit.context === "number" ? limit.context : 2e5;
+	const contextWindow = readContextWindow(raw, limit);
 	return {
 		id,
 		name: typeof raw.name === "string" ? raw.name : id,
@@ -677,6 +712,7 @@ function statusDocument(deps) {
 		models: deps.models,
 		refreshing: deps.refreshing,
 		...deps.credits === void 0 ? {} : { credits: deps.credits },
+		...deps.rateLimit === void 0 ? {} : { rateLimit: deps.rateLimit },
 		...deps.usage === void 0 ? {} : { usage: deps.usage },
 		...deps.signin === void 0 ? {} : { signin: deps.signin },
 		...deps.login === void 0 ? {} : { login: deps.login }
@@ -745,10 +781,18 @@ const MINIMAX_ACCOUNT_HOSTS = {
 	io: "https://agent.minimax.io",
 	com: "https://agent.minimaxi.com"
 };
+/** Open-platform account API, which serves the per-model usage summary. */
+const MINIMAX_OPEN_HOSTS = {
+	cn: "https://www.minimaxi.com",
+	io: "https://www.minimaxi.com",
+	com: "https://www.minimaxi.com"
+};
 /** Membership endpoint: carries the credit summary. */
 const MEMBERSHIP_PATH = "/matrix/api/v1/commerce/get_membership_info";
 /** Credit ledger endpoint: per-grant amounts and expiry. */
 const CREDIT_DETAILS_PATH = "/minimax-cloud/api/v1/credit/details";
+/** Rate-limit window endpoint: the 5-hour and weekly usage the plan meters. */
+const REMAINS_PERCENT_PATH = "/backend/account/token_plan/remains_percent";
 /** OAuth token endpoint. */
 const TOKEN_PATH$1 = "/oauth2/token";
 /** Absolute path of the app's credential file for a region. */
@@ -1053,6 +1097,84 @@ async function fetchCreditLots(credential, region, fetchImpl = fetch) {
 	return lots;
 }
 /**
+* Read the two rate-limit windows out of a remains-percent response.
+*
+* The upstream answers with one entry per metered group; the general one is
+* the only one the plan meters today, and the first entry is used when it is
+* absent. The percents arrive as strings ("19%"), and the counts arrive as -1
+* when the plan does not meter by count, so only the percents and the window
+* edges are read. The window length is derived from the entry's own endpoints
+* rather than assumed to be five hours or seven days — the plan's terms have
+* changed before, and the display should follow whatever the server says.
+*
+* A window the server marks as unlimited (`current_*_status` of 3) carries no
+* allowance to be a percentage of, so it produces no window at all: reporting
+* "0%" of an unlimited quota would be a number nobody can act on.
+*/
+function parseRateLimitWindows(document) {
+	if (typeof document !== "object" || document === null) return void 0;
+	const remains = document.model_remains;
+	if (!Array.isArray(remains) || remains.length === 0) return void 0;
+	const entry = remains.find((item) => typeof item === "object" && item !== null && item.model_name === "general") ?? remains[0];
+	if (typeof entry !== "object" || entry === null) return void 0;
+	const record = entry;
+	const interval = readWindow(record.current_interval_used_percent, record.start_time, record.end_time, record.current_interval_status);
+	const weekly = readWindow(record.current_weekly_used_percent, record.weekly_start_time, record.weekly_end_time, record.current_weekly_status);
+	if (interval === void 0 || weekly === void 0) return void 0;
+	return {
+		interval,
+		weekly
+	};
+}
+/**
+* The status the upstream gives a window that is not limited at all.
+*
+* The desktop app reads it the same way: `isUnlimited: 3 === status`.
+*/
+const UNLIMITED_STATUS = 3;
+/** Assemble one window from its percent and edge fields; all must be present. */
+function readWindow(percent, startAtMs, resetAtMs, status) {
+	if (status === UNLIMITED_STATUS) return void 0;
+	const usedPercent = parsePercent(percent);
+	const start = toNumber$1(startAtMs);
+	const reset = toNumber$1(resetAtMs);
+	if (usedPercent === void 0 || start === void 0 || reset === void 0) return void 0;
+	return {
+		usedPercent,
+		startAtMs: start,
+		resetAtMs: reset
+	};
+}
+/**
+* Read "19%" as 19, and a bare 19 as 19 as well.
+*
+* The desktop app parses both shapes, so both are accepted here: anything
+* unreadable stays unreadable rather than becoming a zero.
+*/
+function parsePercent(value) {
+	if (typeof value === "number") return Number.isFinite(value) ? value : void 0;
+	if (typeof value !== "string") return void 0;
+	const parsed = Number(value.replace(/%\s*$/, ""));
+	return Number.isFinite(parsed) ? parsed : void 0;
+}
+/**
+* Fetch the plan's two rate-limit windows.
+*
+* The endpoint lives on the open-platform host, like the usage summary, and
+* answers the same OAuth credential the membership endpoint takes. The JWT the
+* model gateway accepts does not work here: this is an account endpoint.
+*
+* @returns The windows, or `undefined` when the response carries none.
+*/
+async function fetchRateLimitWindows(credential, region, fetchImpl = fetch) {
+	const response = await fetchImpl(`${MINIMAX_OPEN_HOSTS[region]}${REMAINS_PERCENT_PATH}?business=Agent&device_platform=desktop`, { headers: {
+		accept: "application/json",
+		authorization: `Bearer ${credential.token}`
+	} });
+	if (!response.ok) throw new Error(`rate-limit window request failed: HTTP ${response.status}`);
+	return parseRateLimitWindows(await response.json());
+}
+/**
 * Summarize what is about to expire.
 *
 * Only lots that still hold credits count: a lot that was granted and used up
@@ -1089,6 +1211,9 @@ var MinimaxCredits = class {
 	#expiry;
 	#ledgerAtMs;
 	#ledgerError;
+	#rateLimit;
+	#rateLimitError;
+	#rateLimitAtMs;
 	/** The balance as last read. */
 	get snapshot() {
 		return this.#snapshot;
@@ -1113,12 +1238,26 @@ var MinimaxCredits = class {
 	get ledgerError() {
 		return this.#ledgerError;
 	}
+	/** The plan's rate-limit windows as last read. */
+	get rateLimit() {
+		return this.#rateLimit;
+	}
+	/** Why the windows could not be read, when they could not. */
+	get rateLimitError() {
+		return this.#rateLimitError;
+	}
+	/** When the windows were last read. */
+	get rateLimitAtMs() {
+		return this.#rateLimitAtMs;
+	}
 	/**
 	* Read the balance and record how much was consumed since the last read.
 	*
 	* The credit ledger is read alongside it, but a ledger that cannot be read
 	* never hides the balance: the two come from different endpoints and only
-	* the balance is essential.
+	* the balance is essential. The rate-limit windows ride along under the
+	* same rule — they come from yet another endpoint, and none of the three
+	* takes the others down with it.
 	*
 	* @returns Whether the balance changed.
 	*/
@@ -1141,6 +1280,7 @@ var MinimaxCredits = class {
 			this.#error = error instanceof Error ? error.message : String(error);
 		}
 		await this.refreshLedger(credential, region, fetchImpl, now);
+		await this.refreshRateLimit(credential, region, fetchImpl, now);
 		return changed;
 	}
 	/**
@@ -1161,6 +1301,22 @@ var MinimaxCredits = class {
 			this.#ledgerError = error instanceof Error ? error.message : String(error);
 		}
 	}
+	/**
+	* Read the plan's rate-limit windows.
+	*
+	* Same rule as the ledger: a failure is remembered but never thrown, and a
+	* window that cannot be read leaves the last one on display.
+	*/
+	async refreshRateLimit(credential, region, fetchImpl = fetch, now = Date.now()) {
+		try {
+			const windows = await fetchRateLimitWindows(credential, region, fetchImpl);
+			this.#rateLimit = windows;
+			this.#rateLimitError = windows === void 0 ? "response carried no rate-limit windows" : void 0;
+			this.#rateLimitAtMs = now;
+		} catch (error) {
+			this.#rateLimitError = error instanceof Error ? error.message : String(error);
+		}
+	}
 };
 //#endregion
 //#region src/credentials.ts
@@ -2115,6 +2271,21 @@ function apply(ctx) {
 			...credits.ledgerError === void 0 ? {} : { ledgerError: credits.ledgerError }
 		};
 	};
+	/** The plan's rolling usage windows as the card reads them. */
+	const buildRateLimitStatus = () => {
+		if (creditState === "signed-out" || creditState === "expired") return { state: creditState };
+		const windows = credits.rateLimit;
+		if (windows === void 0) return {
+			state: "unavailable",
+			...credits.rateLimitError === void 0 ? {} : { error: credits.rateLimitError }
+		};
+		return {
+			state: "ok",
+			interval: windows.interval,
+			weekly: windows.weekly,
+			...credits.rateLimitAtMs === void 0 ? {} : { updatedAtMs: credits.rateLimitAtMs }
+		};
+	};
 	/** What this host's own requests have used. */
 	const buildUsageStatus = () => {
 		const totals = meter.totals();
@@ -2217,6 +2388,7 @@ function apply(ctx) {
 			})),
 			refreshing,
 			credits: buildCreditStatus(),
+			rateLimit: buildRateLimitStatus(),
 			usage: buildUsageStatus(),
 			signin: buildSigninStatus(),
 			login: buildLoginStatus()
@@ -2410,4 +2582,4 @@ async function readRequestBody(req) {
 	return text;
 }
 //#endregion
-export { DEVICE_CODE_GRANT, DEVICE_CODE_PATH, EMPTY_USAGE, FALLBACK_MODELS, MEMBERSHIP_PATH, MINIMAXCODE_PROVIDER_ID, MINIMAX_ACTION_PATH, MINIMAX_AUTH_FILENAME, MINIMAX_DATA_DIR, MINIMAX_GATEWAYS, MINIMAX_OAUTH_CLIENT_ID, MINIMAX_REGIONS, MINIMAX_STATUS_PATH, MINIMAX_STREAM_IDLE_TIMEOUT_MS, MODEL_PRICES, MinimaxCatalog, MinimaxCredits, PLUGIN_CREDENTIAL_FILENAME, PLUGIN_STATE_FILENAME, SIGNIN_CLAIM_PATH, SIGNIN_CLAIM_RESULT, SIGNIN_CYCLE_DAYS, SIGNIN_DAY_STATUS, SIGNIN_PANEL_PATH, UsageMeter, apply, authPath, bearerToken, catalogUrl, chatBaseUrl, claimSignin, createMinimaxCodeAdapter, dataDir, daysRemaining, decodeClaims, dshHome, ensureOAuthCredential, estimateCny, expiresInMs, expiryLevel, fetchCreditSummary, fetchSigninPanel, inject, localDay, makePkce, name, parseAuthDocument, parseCatalog, parseCreditSummary, parseOAuthDocument, parseSigninClaim, parseSigninPanel, pluginCredentialPath, pluginStatePath, pollDeviceLogin, priceFor, readCredential, readOAuthCredential, readPluginCredential, readPluginState, refreshOAuthCredential, refreshPluginCredential, startDeviceLogin, statusDocument, timezoneId, writeOAuthCredential, writePluginCredential, writePluginState };
+export { DEVICE_CODE_GRANT, DEVICE_CODE_PATH, EMPTY_USAGE, FALLBACK_MODELS, MEMBERSHIP_PATH, MINIMAXCODE_PROVIDER_ID, MINIMAX_ACTION_PATH, MINIMAX_AUTH_FILENAME, MINIMAX_DATA_DIR, MINIMAX_GATEWAYS, MINIMAX_OAUTH_CLIENT_ID, MINIMAX_REGIONS, MINIMAX_STATUS_PATH, MINIMAX_STREAM_IDLE_TIMEOUT_MS, MODEL_PRICES, MinimaxCatalog, MinimaxCredits, PLUGIN_CREDENTIAL_FILENAME, PLUGIN_STATE_FILENAME, REMAINS_PERCENT_PATH, SIGNIN_CLAIM_PATH, SIGNIN_CLAIM_RESULT, SIGNIN_CYCLE_DAYS, SIGNIN_DAY_STATUS, SIGNIN_PANEL_PATH, UsageMeter, apply, authPath, bearerToken, catalogUrl, chatBaseUrl, claimSignin, createMinimaxCodeAdapter, dataDir, daysRemaining, decodeClaims, dshHome, ensureOAuthCredential, estimateCny, expiresInMs, expiryLevel, fetchCreditSummary, fetchRateLimitWindows, fetchSigninPanel, inject, localDay, makePkce, name, parseAuthDocument, parseCatalog, parseCreditSummary, parseOAuthDocument, parseRateLimitWindows, parseSigninClaim, parseSigninPanel, pluginCredentialPath, pluginStatePath, pollDeviceLogin, priceFor, readCredential, readOAuthCredential, readPluginCredential, readPluginState, refreshOAuthCredential, refreshPluginCredential, startDeviceLogin, statusDocument, timezoneId, writeOAuthCredential, writePluginCredential, writePluginState };

package/package.json

@@ -2,16 +2,24 @@
   "name": "dsh-connect-minimaxcode",
   "displayName": "DSH Connect MiniMax Code",
   "description": "把本机已登录的 MiniMax Code 桌面 App 模型接入 DeepSeek Harness：零配置、Anthropic Messages 兼容、动态模型目录，并显示积分余额与到期 — bring MiniMax Code desktop app models into DSH with a dynamic model catalog and a credit balance with expiry details.",
-  "version": "0.5.3",
+  "version": "0.5.5",
   "author": "JeffTsuiCUG",
   "contributors": [
     {
       "name": "JeffTsuiCUG",
       "url": "https://github.com/JeffTsuiCUG"
     },
+    {
+      "name": "eghrhegpe",
+      "url": "https://github.com/eghrhegpe"
+    },
+    {
+      "name": "qzz19970504",
+      "url": "https://github.com/qzz19970504"
+    },
     {
-      "name": "eghrhegpe",
-      "url": "https://github.com/eghrhegpe"
+      "name": "azsora",
+      "url": "https://github.com/azsora"
     }
   ],
   "license": "MIT",