opencode-zen-freex 0.2.13 → 0.2.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/MAINTAINING.md CHANGED
@@ -28,13 +28,19 @@ model whose own vendor publishes 1048576/131072. The ids the tier added on
28
28
  against a declared 65536, and `glm-5.3-flash-free` is declared 200000/32000
29
29
  while its paid twin `glm-5.3-flash` is declared 1000000/131072 in the same
30
30
  catalogue — and a 232685-token prompt was served through the free id, which the
31
- declared window does not allow.
32
-
33
- Both numbers are acted on. The window decides when a conversation is compacted
34
- and how much of it is ever sent; the output cap is sent as `max_tokens` on every
35
- request, so a reply is cut at it with a finish reason that reads like the
36
- model's own decision. A window that is too small is never refused, it is just
37
- quietly never used, which is why this stayed invisible for so long.
31
+ declared window does not allow. `space-bunny-free` under-reports on a third
32
+ axis, its `input`: the catalogue derives that number from its own pair
33
+ (`context − output`, 524288) while prompts of 535,110, 935,110 and 979,550
34
+ tokens were served through the free id, and the axis is what a host that shows
35
+ a window shows — magpie's `context_window` and `max_input_tokens` both follow
36
+ it, so the derivation was on screen as half a window.
37
+
38
+ All of these numbers are acted on. The window decides when a conversation is
39
+ compacted and how much of it is ever sent; the output cap is sent as
40
+ `max_tokens` on every request, so a reply is cut at it with a finish reason that
41
+ reads like the model's own decision; the `input` axis is the size a
42
+ window-showing host displays. A window that is too small is never refused, it is
43
+ just quietly never used, which is why this stayed invisible for so long.
38
44
 
39
45
  `limits.mjs` holds what was measured, per axis, with the catalogue value it was
40
46
  measured against. Each axis carries `samples` and `how`; the short of it:
@@ -51,6 +57,7 @@ measured against. Each axis carries `samples` and `how`; the short of it:
51
57
  | `ll-alpha-free` | output | 262144 | the ceiling the route's own refusal names, against a declared 65536 |
52
58
  | `glm-5.3-flash-free` | context | 1000000 | what this route declares for the same upstream model, with a 232685-token prompt served as witness |
53
59
  | `glm-5.3-flash-free` | output | 131072 | what this route declares for the same upstream model |
60
+ | `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 |
54
61
 
55
62
  A prompt sized just over the window is refused with
56
63
 
@@ -74,6 +81,14 @@ figure is a rough one (characters, not tokens) and must not be read as a count.
74
81
  A second upstream words the same fact as "This endpoint's maximum context length
75
82
  is …" and breaks the request into text input, tool input and output.
76
83
 
84
+ **The input**, the third axis: nothing cheap names it — the refusals on this
85
+ route name the window, and this id's own refusal names nothing at all — so it is
86
+ measured by serving. A prompt sized past the declared input is the measurement
87
+ (535,110, 935,110 and 979,550-token prompts each came back with the needle at
88
+ their end echoed, and `usage.prompt_tokens` is the count that says how much was
89
+ served), and the window the catalogue declares for the same id bounds the value
90
+ from above: a request placed over it is refused.
91
+
77
92
  The ceiling, which is cheaper than the window: ask for `max_tokens: 1000000` on a
78
93
  short prompt and stop reading as soon as the answer starts. An upstream that
79
94
  validates the ceiling refuses and names it — `max_tokens is too large: 1000000.
@@ -104,7 +119,8 @@ own, which is the intended end state.
104
119
  that model's window for the rest of the process. The list is rebuilt at every
105
120
  start and hourly after, so a route that changes the window it enforces is
106
121
  followed without anyone editing this file. Nothing is persisted: a restart falls
107
- back to what is measured here.
122
+ back to what is measured here. The `input` axis has no live form: the refusals
123
+ this route sends name a window and a completion ceiling, and never an input cap.
108
124
 
109
125
  **The same shape on a second upstream.** `mimo-v2.6-flash-free` is declared
110
126
  200000/32000 here too, and its window is a route figure like the one above — an
package/README.md CHANGED
@@ -45,7 +45,7 @@ magpie plugin login opencode-zen-free
45
45
 
46
46
  插件会去发现 Zen 当前的免费模型,包括它们的上下文窗口和思考(reasoning)等级。用 `opencode-zen-free/<模型名>`,例如 `opencode-zen-free/big-pickle`。
47
47
 
48
- 免费模型的目录上限有时被 Zen 少报,而少报的那一边没有谁会报错:`deepseek-v4.1-flash-free` 在目录里是 20 万上下文 / 3.2 万输出,而同一上游模型的付费 id 是 100 万 / 38.4 万。上下文窗口太小只会让宿主安静地早点压缩,输出上限太小会把回复截断成看起来像模型自己停下的样子,所以插件对这类模型按实测与路由自述对齐(依据与复测方法见 `MAINTAINING.md` 的 “Limits Zen under-reports”),并在运行中采用上游自报的窗口。
48
+ 免费模型的目录上限有时被 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”),并在运行中采用上游自报的窗口。
49
49
 
50
50
  已下线的模型和 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)提供,目录晚一步也不影响。
51
51
 
package/limits.mjs CHANGED
@@ -12,9 +12,17 @@
12
12
  // output cap that is too small cuts replies off with a finish reason that looks
13
13
  // like the model's own decision.
14
14
  //
15
+ // The input axis is the third, and it fails the same way one layer out. A host
16
+ // that plans what to send reads it as the room a prompt has; a host that shows a
17
+ // model's window reads it as the window itself — measured 2026-10-16, magpie's
18
+ // `context_window` and `max_input_tokens` both follow `limit.input` when one is
19
+ // declared. So an input axis that under-reports is not only never used, it is
20
+ // what a user is shown as the model's size.
21
+ //
15
22
  // Only evidence moves a value here, and evidence is sorted:
16
23
  //
17
- // route the route's own refusal, in its own words
24
+ // route the route's own answer about its own limit: the words of a
25
+ // refusal, or what its own service demonstrates
18
26
  // route-twin what this route declares for the same upstream model
19
27
  // vendor the model vendor's published page
20
28
  // witnessed a generation somebody watched finish
@@ -128,6 +136,19 @@ export const LIMITS = {
128
136
  how: "the same paid twin declares 131072 on this axis",
129
137
  },
130
138
  },
139
+ // Measured the day a host's window for this id was reported half its size.
140
+ // Only the input axis moves: the window and the ceiling are what this route
141
+ // declares, and what was served agrees with both.
142
+ "space-bunny-free": {
143
+ input: {
144
+ value: 1048576,
145
+ source: "route",
146
+ declaredAt: 524288,
147
+ measured: "2026-10-16",
148
+ 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",
149
+ 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.",
150
+ },
151
+ },
131
152
  };
132
153
 
133
154
  // "This model's maximum context length is 1048576 tokens. However, you
@@ -443,7 +464,7 @@ export function limitOverrides(
443
464
  // an object handed in as `table` carries — evidence for a model nobody
444
465
  // declared, from a table that never named it.
445
466
  const record = table && Object.hasOwn(table, id) ? table[id] : undefined;
446
- for (const axis of ["context", "output"]) {
467
+ for (const axis of ["context", "input", "output"]) {
447
468
  // Own property, like the table lookup two lines up: `declared` is handed in
448
469
  // by a caller, and a `context` inherited from a custom prototype — or from a
449
470
  // polluted `Object.prototype` — would otherwise be read as a declaration the
@@ -451,7 +472,12 @@ export function limitOverrides(
451
472
  // check with a number nobody declared.
452
473
  const declaredValue = declared && Object.hasOwn(declared, axis) ? declared[axis] : undefined;
453
474
  const entry = record?.[axis];
454
- const live = (axis === "context" ? observed : observedOutput)?.get(id);
475
+ // Only the axes a refusal names have a live form — a window and a
476
+ // completion ceiling. An input axis is answered from the table alone: the
477
+ // refusals this route sends name the window that bounds it, never an input
478
+ // cap of its own, so there is nothing to observe into it.
479
+ const live =
480
+ (axis === "context" ? observed : axis === "output" ? observedOutput : undefined)?.get(id);
455
481
  // A route statement made while this process was running is the same tier as
456
482
  // the table and newer than it, so it is taken as it stands. Everything else
457
483
  // has to have been measured against the catalogue in front of us now: the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-zen-freex",
3
- "version": "0.2.13",
3
+ "version": "0.2.14",
4
4
  "description": "OpenCode Zen's free models, for hosts that are not OpenCode: the public credential, automatic discovery and native streaming protocols",
5
5
  "type": "module",
6
6
  "main": "./index.mjs",