opencode-zen-freex 0.2.12 → 0.2.14

package/MAINTAINING.md

@@ -22,13 +22,25 @@ small. `deepseek-v4.1-flash-free` is declared 200000/32000 while
 `deepseek-v4.1-flash` — the paid id serving the same upstream model, which
 `x-opencode-upstream-model-id` confirms — is declared 1000000/384000 in that
 same catalogue, and `mimo-v2.6-flash-free` is declared 200000/32000 against a
-model whose own vendor publishes 1048576/131072.
-
-Both numbers are acted on. The window decides when a conversation is compacted
-and how much of it is ever sent; the output cap is sent as `max_tokens` on every
-request, so a reply is cut at it with a finish reason that reads like the
-model's own decision. A window that is too small is never refused, it is just
-quietly never used, which is why this stayed invisible for so long.
+model whose own vendor publishes 1048576/131072. The ids the tier added on
+2026-10-16 were under-reported the same way on the day they appeared:
+`ll-alpha-free` names a 262144-token completion ceiling in its own refusal
+against a declared 65536, and `glm-5.3-flash-free` is declared 200000/32000
+while its paid twin `glm-5.3-flash` is declared 1000000/131072 in the same
+catalogue — and a 232685-token prompt was served through the free id, which the
+declared window does not allow. `space-bunny-free` under-reports on a third
+axis, its `input`: the catalogue derives that number from its own pair
+(`context − output`, 524288) while prompts of 535,110, 935,110 and 979,550
+tokens were served through the free id, and the axis is what a host that shows
+a window shows — magpie's `context_window` and `max_input_tokens` both follow
+it, so the derivation was on screen as half a window.
+
+All of these numbers are acted on. The window decides when a conversation is
+compacted and how much of it is ever sent; the output cap is sent as
+`max_tokens` on every request, so a reply is cut at it with a finish reason that
+reads like the model's own decision; the `input` axis is the size a
+window-showing host displays. A window that is too small is never refused, it is
+just quietly never used, which is why this stayed invisible for so long.
 
 `limits.mjs` holds what was measured, per axis, with the catalogue value it was
 measured against. Each axis carries `samples` and `how`; the short of it:
@@ -42,6 +54,10 @@ measured against. Each axis carries `samples` and `how`; the short of it:
 | `big-pickle` | output | 131072 | the ceiling the route names when it is asked for too much |
 | `nemotron-3.5-lightning-free` | context | 1000000 | the route's own refusal, in its own words |
 | `longcat-2.5-preview-free` | output | 262144 | the ceiling the route names when it is asked for too much |
+| `ll-alpha-free` | output | 262144 | the ceiling the route's own refusal names, against a declared 65536 |
+| `glm-5.3-flash-free` | context | 1000000 | what this route declares for the same upstream model, with a 232685-token prompt served as witness |
+| `glm-5.3-flash-free` | output | 131072 | what this route declares for the same upstream model |
+| `space-bunny-free` | input | 1048576 | the window this route declares for the same id, with prompts of up to nearly twice the declared input served |
 
 A prompt sized just over the window is refused with
 
@@ -65,6 +81,14 @@ figure is a rough one (characters, not tokens) and must not be read as a count.
 A second upstream words the same fact as "This endpoint's maximum context length
 is …" and breaks the request into text input, tool input and output.
 
+**The input**, the third axis: nothing cheap names it — the refusals on this
+route name the window, and this id's own refusal names nothing at all — so it is
+measured by serving. A prompt sized past the declared input is the measurement
+(535,110, 935,110 and 979,550-token prompts each came back with the needle at
+their end echoed, and `usage.prompt_tokens` is the count that says how much was
+served), and the window the catalogue declares for the same id bounds the value
+from above: a request placed over it is refused.
+
 The ceiling, which is cheaper than the window: ask for `max_tokens: 1000000` on a
 short prompt and stop reading as soon as the answer starts. An upstream that
 validates the ceiling refuses and names it — `max_tokens is too large: 1000000.
@@ -95,7 +119,8 @@ own, which is the intended end state.
 that model's window for the rest of the process. The list is rebuilt at every
 start and hourly after, so a route that changes the window it enforces is
 followed without anyone editing this file. Nothing is persisted: a restart falls
-back to what is measured here.
+back to what is measured here. The `input` axis has no live form: the refusals
+this route sends name a window and a completion ceiling, and never an input cap.
 
 **The same shape on a second upstream.** `mimo-v2.6-flash-free` is declared
 200000/32000 here too, and its window is a route figure like the one above — an

package/README.md

@@ -45,9 +45,9 @@ magpie plugin login opencode-zen-free
 
 插件会去发现 Zen 当前的免费模型，包括它们的上下文窗口和思考（reasoning）等级。用 `opencode-zen-free/<模型名>`，例如 `opencode-zen-free/big-pickle`。
 
-免费模型的目录上限有时被 Zen 少报，而少报的那一边没有谁会报错：`deepseek-v4.1-flash-free` 在目录里是 20 万上下文 / 3.2 万输出，而同一上游模型的付费 id 是 100 万 / 38.4 万。上下文窗口太小只会让宿主安静地早点压缩，输出上限太小会把回复截断成看起来像模型自己停下的样子，所以插件对这类模型按实测与路由自述对齐（依据与复测方法见 `MAINTAINING.md` 的 “Limits Zen under-reports”），并在运行中采用上游自报的窗口。
+免费模型的目录上限有时被 Zen 少报，而少报的那一边没有谁会报错：`deepseek-v4.1-flash-free` 在目录里是 20 万上下文 / 3.2 万输出，而同一上游模型的付费 id 是 100 万 / 38.4 万。上下文窗口太小只会让宿主安静地早点压缩，输出上限太小会把回复截断成看起来像模型自己停下的样子；`input` 这一轴同样会被少报——有些宿主显示的「上下文窗口」取的就是它（magpie 如此），而 `space-bunny-free` 的 `input` 是目录自己按 `context − output` 推出的 52.4 万，实测 97.9 万 token 的 prompt 都被完整服务、结尾的暗号原样复述。所以插件对这类模型按实测与路由自述对齐（依据与复测方法见 `MAINTAINING.md` 的 “Limits Zen under-reports”），并在运行中采用上游自报的窗口。
 
-已下线的模型和 SystemOne 模型会被排除。这份列表在宿主每次列举模型时重新获取（magpie 在启动时做一次，之后每小时一次）：Zen 不再免费开放的模型会退出列表，新转为免费的模型会加入列表——**不等** OpenCode 的目录或文档写到它：只要 Zen 的列表里有、id 里带 `-free`，就按 provider 自己的协议（OpenAI 兼容 / chat）提供，目录晚一步也不影响。
+已下线的模型和 SystemOne 模型会被排除：「下线」指的是状态写着 `retired`/`disabled`，或带着已生效的退役日期。目录里标了 `deprecated` 但 Zen 的列表里还在的模型**照常提供**——`deprecated` 是预告，而「还在不在」由列表说了算（实测 2026-10-16：`muse-spark-1.2-contributor-free` 在目录里是 `deprecated`，Zen 仍在服务它，把它当退役就把一个能用的免费模型藏掉了）。这份列表在宿主每次列举模型时重新获取（magpie 在启动时做一次，之后每小时一次）：Zen 不再免费开放的模型会退出列表，新转为免费的模型会加入列表——**不等** OpenCode 的目录或文档写到它：只要 Zen 的列表里有、id 里带 `-free`，就按 provider 自己的协议（OpenAI 兼容 / chat）提供，目录晚一步也不影响。
 
 目录或文档读不到时**不算 fallback**：Zen 的列表已经读到了，它就是当前该提供的东西；报成 fallback 会让宿主保守地沿用上一次完整读到的列表，于是读不到 `raw.githubusercontent.com` 或 `models.opencode.ai` 的机器永远看不到之后新转免费的模型。只有**列表本身**读不到才沿用上一次结果；第一次还没读到之前，用的是打包在插件里的那份，所以这个 provider 不会空着。请求一个当前并不免费的模型，会得到一个 404 并列出当时免费的模型；若某个模型是在上次列举之后才转免费的，请求会在重新获取列表后照常服务（最多每分钟一次）。可用性和限流由 Zen 决定，插件这边拿不到剩余额度。
 

package/limits.mjs

@@ -12,9 +12,17 @@
 // output cap that is too small cuts replies off with a finish reason that looks
 // like the model's own decision.
 //
+// The input axis is the third, and it fails the same way one layer out. A host
+// that plans what to send reads it as the room a prompt has; a host that shows a
+// model's window reads it as the window itself — measured 2026-10-16, magpie's
+// `context_window` and `max_input_tokens` both follow `limit.input` when one is
+// declared. So an input axis that under-reports is not only never used, it is
+// what a user is shown as the model's size.
+//
 // Only evidence moves a value here, and evidence is sorted:
 //
-//   route       the route's own refusal, in its own words
+//   route       the route's own answer about its own limit: the words of a
+//               refusal, or what its own service demonstrates
 //   route-twin  what this route declares for the same upstream model
 //   vendor      the model vendor's published page
 //   witnessed   a generation somebody watched finish
@@ -96,20 +104,75 @@ export const LIMITS = {
       how: "\"Upstream request failed: [invalid_parameter] 参数校验失败: /max_tokens: 1000000 is not less or equal to 262144\" — the second wording namedOutputCap reads, where the ceiling is the number max_tokens has to stay under. Its context needs nothing: the catalogue's 1000000 is what that same refusal calls the endpoint's window.",
     },
   },
+  // The two the free tier added on 2026-10-16, each measured the day it was
+  // noticed. Both under-report in the catalogue the same way the older entries
+  // do, and both were checked on every axis: nothing below is what a refusal
+  // happened to say, it is all that was asked.
+  "ll-alpha-free": {
+    output: {
+      value: 262144,
+      source: "route",
+      declaredAt: 65536,
+      measured: "2026-10-16",
+      samples: "max_completion_tokens 1000000 and 300000 both refused, each naming 262144; nothing above 65536 watched — the ceiling is the route's own number, four times what the catalogue declares",
+      how: "\"Upstream request failed: [400] max_completion_tokens is too large: 300000.This model supports at most 262144 completion tokens.\" — the ceiling is the number the sentence names. Its context needs nothing: the same day's refusal, \"The input (341480 tokens) is longer than the model's context length (262144 tokens).\", is the window the catalogue already declares.",
+    },
+  },
+  "glm-5.3-flash-free": {
+    context: {
+      value: 1000000,
+      source: "route-twin",
+      declaredAt: 200000,
+      measured: "2026-10-16",
+      samples: "a 232685-token prompt was served and answered from (usage.prompt_tokens 232685), so the declared 200000 is already known to be small; nothing above it was refused, because this upstream refuses no max_tokens at all",
+      how: "glm-5.3-flash, the paid id serving the same upstream model — the catalogue's own canonical_model_id for this free id is zhipuai/glm-5.3-flash — is declared 1000000 in this same catalogue",
+    },
+    output: {
+      value: 131072,
+      source: "route-twin",
+      declaredAt: 32000,
+      measured: "2026-10-16",
+      samples: "max_tokens 4000000 was accepted with no refusal at all, which is the DeepSeek upstream's shape: silence here is not evidence of a ceiling either way, and nothing above 32000 was watched",
+      how: "the same paid twin declares 131072 on this axis",
+    },
+  },
+  // Measured the day a host's window for this id was reported half its size.
+  // Only the input axis moves: the window and the ceiling are what this route
+  // declares, and what was served agrees with both.
+  "space-bunny-free": {
+    input: {
+      value: 1048576,
+      source: "route",
+      declaredAt: 524288,
+      measured: "2026-10-16",
+      samples: "prompts of 535,110, 935,110 and 979,550 tokens served whole, each with the needle at the end of it echoed back and each counted by `usage.prompt_tokens`, so the declared 524288 is already known to be small; a prompt placed over the window was refused 400, in words that name nothing",
+      how: "the catalogue's 524288 is its own `context − output` (1048576 − 524288) read as a cap, and this route does not enforce it: the samples above run from just past the declared cap to nearly twice it, served whole, and the wall is the 1048576-token window this same catalogue declares for this id. A host that shows the input axis shows the window — magpie's `context_window` and `max_input_tokens` are both this field when one is declared — so a derivation left here is a wrong window on screen.",
+    },
+  },
 };
 
 // "This model's maximum context length is 1048576 tokens. However, you
 // requested 1422278 tokens (1038278 in the messages, 384000 in the
-// completion)." — the route's own words, and the only sentence seen on this
-// route that states a window. A second upstream phrases the same fact as "This
-// endpoint's maximum context length is ...", with the request broken into text
-// input, tool input and output; both are the route naming its own window, and
-// its "requested about" figure is a rough one (chars, not tokens) rather than
-// the count a served request reports in `usage.prompt_tokens`. A generic 400
-// says nothing attributable and is left alone; §7 of the measured notes has a
-// context overflow and an invalid parameter answering with byte-identical 400s
+// completion)." — the route's own words, and the sentence seen most often on
+// this route that states a window. A second upstream phrases the same fact as
+// "This endpoint's maximum context length is ...", with the request broken into
+// text input, tool input and output; both are the route naming its own window,
+// and its "requested about" figure is a rough one (chars, not tokens) rather
+// than the count a served request reports in `usage.prompt_tokens`. A generic
+// 400 says nothing attributable and is left alone; §7 of the measured notes has
+// a context overflow and an invalid parameter answering with byte-identical 400s
 // on another Zen model.
-const NAMED_CONTEXT = /maximum context length is (\d+) tokens/id;
+//
+// A third wording states the same fact as a parenthetical, and was missed until
+// it was measured: "The input (341480 tokens) is longer than the model's context
+// length (262144 tokens)." (`ll-alpha-free`, 2026-10-16). It names the same
+// number in the same sentence, so it is read the same way — a window this file
+// does not read is a window the plugin keeps under-declaring, which is the one
+// failure it exists to remove.
+const NAMED_CONTEXT = [
+  /maximum context length is (\d+) tokens/id,
+  /context length \((\d+) tokens?\)/id,
+];
 
 // "max_tokens is too large: 200000. This model supports at most 131072 completion
 // tokens, whereas you provided 200000." — an upstream that validates the ceiling
@@ -169,7 +232,7 @@ function describe({ kind, id, axis, value, measuredAgainst, declared }) {
 // The window a refusal names, or undefined when the body says nothing
 // attributable. Exported for the tests and for anyone reading a capture.
 export function namedContextWindow(text) {
-  return namedFrom([NAMED_CONTEXT], text)?.value;
+  return namedFrom(NAMED_CONTEXT, text)?.value;
 }
 
 // The completion ceiling a refusal names, or undefined. Same rule as the window:
@@ -373,7 +436,7 @@ function digitsEnd(found) {
 // returned cannot be two answers.
 function namedAxes(text, limit, cut) {
   const head = text.slice(0, limit);
-  const context = namedFrom([NAMED_CONTEXT], head);
+  const context = namedFrom(NAMED_CONTEXT, head);
   const output = namedFrom(NAMED_OUTPUT, head);
   const onCut = (found) => cut && found !== undefined && digitsEnd(found) >= head.length;
   return {
@@ -401,7 +464,7 @@ export function limitOverrides(
   // an object handed in as `table` carries — evidence for a model nobody
   // declared, from a table that never named it.
   const record = table && Object.hasOwn(table, id) ? table[id] : undefined;
-  for (const axis of ["context", "output"]) {
+  for (const axis of ["context", "input", "output"]) {
     // Own property, like the table lookup two lines up: `declared` is handed in
     // by a caller, and a `context` inherited from a custom prototype — or from a
     // polluted `Object.prototype` — would otherwise be read as a declaration the
@@ -409,7 +472,12 @@ export function limitOverrides(
     // check with a number nobody declared.
     const declaredValue = declared && Object.hasOwn(declared, axis) ? declared[axis] : undefined;
     const entry = record?.[axis];
-    const live = (axis === "context" ? observed : observedOutput)?.get(id);
+    // Only the axes a refusal names have a live form — a window and a
+    // completion ceiling. An input axis is answered from the table alone: the
+    // refusals this route sends name the window that bounds it, never an input
+    // cap of its own, so there is nothing to observe into it.
+    const live =
+      (axis === "context" ? observed : axis === "output" ? observedOutput : undefined)?.get(id);
     // A route statement made while this process was running is the same tier as
     // the table and newer than it, so it is taken as it stands. Everything else
     // has to have been measured against the catalogue in front of us now: the

package/models.mjs

@@ -44,15 +44,23 @@ const hasValue = (value) => value !== null && value !== undefined;
 // offered. A status that is set — "active" included — is still read as itself.
 const isSet = (value) => hasValue(value) && String(value).trim() !== "";
 
+// A status ends a model when it says the model is gone: "retired" and
+// "disabled" are endings. "deprecated" is not one — it says the catalogue
+// expects the model to go, and what decides whether it is still there is the
+// list Zen serves, which discovery already reads: measured 2026-10-16,
+// `muse-spark-1.2-contributor-free` is marked deprecated in the catalogue while
+// Zen lists it and the free tier answers a request for it through this plugin,
+// so reading that status as an ending hid a model that was being served.
+const ENDED = ["retired", "disabled"];
+
 function isRetired(model) {
   return (
     model.deprecated === true ||
-    ["deprecated", "retired", "disabled"].includes(
-      isSet(model.status) ? model.status : model.lifecycle,
-    ) ||
+    ENDED.includes(isSet(model.status) ? model.status : model.lifecycle) ||
     // Read through `isSet`, not `hasValue`: a blank `deprecated_at` is the empty
     // string the catalogue writes for a date it does not have, and reading it as
-    // a date retired a model that was still on offer.
+    // a date retired a model that was still on offer. An effective date is an
+    // ending whatever the status beside it says.
     isSet(model.deprecated_at) ||
     isSet(model.retirement_date)
   );
@@ -191,10 +199,19 @@ export const bootstrapProtocols = {
   "nemotron-3.5-lightning-free": "chat",
   "muse-spark-1.3-contributor-free": "responses",
   "jev-1.13-free": "systemone",
+  // The free tier's list on 2026-10-16, when these five appeared: the four chat
+  // ones and the responses one below, whose paid twin the docs table names.
+  "deepseek-v4.1-flash-free": "chat",
+  "glm-5.3-flash-free": "chat",
+  "ll-alpha-free": "chat",
+  "nemotron-3.5-super-vl-free": "chat",
+  "muse-spark-1.2-contributor-free": "responses",
 };
 
-// Offline bootstrap metadata from the OpenCode catalog, 2026-10-06; the
-// free models listed since added on 2026-10-15.
+// Offline bootstrap metadata from the OpenCode catalog, 2026-10-06; the free
+// models listed since added on 2026-10-15, and the ids the tier was serving on
+// 2026-10-16 added then. A host that reaches nothing on its first run offers
+// these; the first discovery replaces the list.
 export const bootstrapProvider = {
   npm: SDK.chat,
   models: {
@@ -270,6 +287,66 @@ export const bootstrapProvider = {
         { type: "effort", values: ["minimal", "low", "medium", "high", "xhigh"] },
       ],
     },
+    // The free ids the tier was serving on 2026-10-16 and this snapshot did not
+    // carry. Their numbers are the catalogue's, as every other entry here is —
+    // `limits.mjs` is what corrects the ones the catalogue under-reports, and it
+    // carries entries for two of these.
+    "deepseek-v4.1-flash-free": {
+      name: "DeepSeek V4.1 Flash Free",
+      cost: { input: 0, output: 0 },
+      limit: { context: 200000, output: 32000 },
+      reasoning: true,
+      tool_call: true,
+      interleaved: { field: "reasoning_content" },
+      modalities: { input: ["text", "image"], output: ["text"] },
+      reasoning_options: [{ type: "effort", values: ["low", "high", "max"] }],
+    },
+    "glm-5.3-flash-free": {
+      name: "GLM-5.3-Flash Free",
+      cost: { input: 0, output: 0 },
+      limit: { context: 200000, output: 32000 },
+      reasoning: true,
+      tool_call: true,
+      interleaved: { field: "reasoning_content" },
+      modalities: { input: ["text", "image", "video", "pdf"], output: ["text"] },
+      reasoning_options: [{ type: "effort", values: ["low", "high", "max"] }],
+    },
+    "ll-alpha-free": {
+      name: "LL Alpha Free",
+      cost: { input: 0, output: 0 },
+      limit: { context: 262144, output: 65536 },
+      reasoning: true,
+      tool_call: true,
+      interleaved: { field: "reasoning_content" },
+      modalities: { input: ["text"], output: ["text"] },
+      reasoning_options: [
+        { type: "effort", values: ["low", "medium", "high", "xhigh", "max"] },
+      ],
+    },
+    "nemotron-3.5-super-vl-free": {
+      name: "Nemotron 3.5 Super VL Free",
+      cost: { input: 0, output: 0 },
+      limit: { context: 1048576, output: 131072 },
+      reasoning: true,
+      tool_call: true,
+      interleaved: { field: "reasoning_content" },
+      modalities: { input: ["text", "image"], output: ["text"] },
+      reasoning_options: [
+        { type: "effort", values: ["none", "minimal", "low", "medium", "high", "xhigh"] },
+      ],
+    },
+    "muse-spark-1.2-contributor-free": {
+      name: "Muse Spark 1.2 Free",
+      cost: { input: 0, output: 0 },
+      provider: { npm: SDK.responses },
+      limit: { context: 1048576, output: 131072 },
+      reasoning: true,
+      tool_call: true,
+      modalities: { input: ["text", "image", "video", "pdf", "audio"], output: ["text"] },
+      reasoning_options: [
+        { type: "effort", values: ["minimal", "low", "medium", "high", "xhigh"] },
+      ],
+    },
   },
 };
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-zen-freex",
-  "version": "0.2.12",
+  "version": "0.2.14",
   "description": "OpenCode Zen's free models, for hosts that are not OpenCode: the public credential, automatic discovery and native streaming protocols",
   "type": "module",
   "main": "./index.mjs",