opencode-zen-freex 0.2.3 → 0.2.5

package/MAINTAINING.md

@@ -21,7 +21,8 @@ ids the catalogue is wrong in the one direction nothing complains about: too
 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.
+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
@@ -32,10 +33,12 @@ 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:
 
-| axis | value | from |
-| --- | --- | --- |
-| context | 1048576 | the route's own refusal, in its own words |
-| output | 384000 | what this route declares for the same upstream model |
+| id | axis | value | from |
+| --- | --- | --- | --- |
+| `deepseek-v4.1-flash-free` | context | 1048576 | the route's own refusal, in its own words |
+| `deepseek-v4.1-flash-free` | output | 384000 | what this route declares for the same upstream model |
+| `mimo-v2.6-flash-free` | context | 1048576 | the route's own refusal, in its own words |
+| `mimo-v2.6-flash-free` | output | 131072 | the vendor's own catalogue entry |
 
 A prompt sized just over the window is refused with
 
@@ -53,10 +56,20 @@ published what that model does; a single reply of 306,880 completion tokens
 number out of the refusal, three times, interleaved, per the rule below. The
 filler measured 4.887 characters per token with about 1700 tokens of fixed
 request overhead, and a request that is *served* says nothing about where the
-wall is. The output: re-read the paid id's `limit` in
-`https://models.opencode.ai/api.json`. A value Zen accepts is not evidence —
-`max_tokens: 2000000` under a short prompt answers 200 and writes nothing like
-it — and neither is a generation nobody watched finish.
+wall is — it is what the calibration is checked against, since
+`usage.prompt_tokens` is the real count while the refusal's "requested about"
+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 output: a paid twin's `limit` in `https://models.opencode.ai/api.json` is
+the stronger source, and re-reading it is the whole job. With no twin — `mimo`
+has none — the figure rests on the vendor's own entry, which is weaker evidence
+and has to say so in `samples`: what is declared is what a vendor publishes, not
+something watched. A value Zen accepts is not evidence — `max_tokens: 2000000`
+under a short prompt answers 200 and writes nothing like it, and `mimo`'s refusal
+came back with the 200000 it was asked for rather than with a ceiling — and
+neither is a generation nobody watched finish.
 
 **What voids it.** Each axis records the catalogue value it was measured
 against, and an axis whose declaration moved is dropped rather than kept: a
@@ -71,10 +84,24 @@ 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.
 
-**A lead, not evidence.** `mimo-v2.6-flash-free` is declared 200000/32000 here
-too, and another plugin on this route has reported Zen answering that id with
-`maximum context length is 1048576 tokens`. That is somebody else's measurement
-of a different id, so it is not in `limits.mjs`: measure it before adding it.
+**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
+850,249 token prompt was served first, its needle echoed back, and then a prompt
+just over the wall was refused with
+
+```
+This endpoint's maximum context length is 1048576 tokens. However, you requested
+about 1496523 tokens (1295079 of text input, 1444 of tool input, 200000 in the
+output).
+```
+
+which is the route naming its own window, on an upstream that words it
+differently from the DeepSeek ids. Its output is the first figure in this file
+resting on a vendor page: that same refusal came back with the 200000 it was
+asked for, unclamped, so this route states no completion ceiling of its own, and
+131072 is Xiaomi's entry for `mimo-v2.6-flash` (`api.xiaomimimo.com`, and its
+China token plan). Nothing above 32000 has been watched on this route, and
+`samples` says that rather than implying a witness.
 
 ## The loop
 
@@ -187,24 +214,34 @@ either way, so one stays in place whichever is installed. It does mean the two
 are mutually exclusive — installing both leaves two plugins claiming one
 provider id, and which one wins is down to load order. Pick one.
 
-To publish: bump `version`, `npm publish`, and tag. `magpie plugin add
-opencode-zen-freex` installs it by that name.
+To publish: bump `version`, commit, `npm publish` in a terminal, and tag — in
+that order, so the tarball, the commit the tag names, and the tree both were
+built from are one thing. `magpie plugin add opencode-zen-freex` installs it by
+that name.
 
-**The second factor is a browser, not a password.** Run `npm publish`; when the
-account has 2FA on, the command stops with `EOTP` and prints
+**The second factor is a browser, not a password.** Run `npm publish` in a
+terminal. When the account has 2FA on, the command stops and offers the whole
+exchange at once:
 
 ```
+Authenticate your account at:
 https://www.npmjs.com/auth/cli/...
+Press ENTER to open in the browser...
 ```
 
-Open that address, authorize there, and the same command carries on by itself.
-Nothing is typed back into the terminal and nothing is passed to a script: the
-address is tied to the browser session that printed it and is different every
-time, so it is read out of the running command's own output rather than composed
-in advance. That address belongs to whoever is at the browser, so they are the
-one who authorizes — the command can sit in the background while they do, and it
-needs no more than the one click. Opening it is a convenience, not a step: a
-`start` (Windows) or `open` (macOS) on the URL is the whole of it.
+Press ENTER, authorize in the browser, and the same command carries on by
+itself. Nothing is typed back into the terminal and nothing is passed to a
+script: the address is tied to the browser session that printed it and differs
+every time, so it is read out of the running command rather than composed in
+advance. Whoever is at the browser authorizes, so the command can be started for
+them and left waiting — the one thing it needs from them is the ENTER that opens
+it.
+
+Both halves of that depend on the command having a terminal. Run as a background
+job or piped into a file, npm has no browser to offer, redacts the address to
+`https://www.npmjs.com/auth/cli/***` and exits `EOTP` rather than waiting, so a
+log of the failed attempt cannot be used to finish it — start it again in a
+terminal.
 
 An account with no second factor to give publishes in one step. So does
 `npm login --auth-type=web`, which is the same browser exchange kept as a

package/limits.mjs

@@ -48,14 +48,37 @@ export const LIMITS = {
       how: "deepseek-v4.1-flash, the paid id serving the same upstream model, is declared 384000 in this same catalogue; DeepSeek's own page says 384K, which is 393216 read as binary K",
     },
   },
+  "mimo-v2.6-flash-free": {
+    context: {
+      value: 1048576,
+      source: "route",
+      declaredAt: 200000,
+      measured: "2026-10-15",
+      samples: "an 850,249 token prompt served, its needle echoed back; a prompt just over the window refused 400",
+      how: "a different upstream from the DeepSeek ids, and it says so in its own words: \"This endpoint's maximum context length is 1048576 tokens. However, you requested about 1496523 tokens (1295079 of text input, 1444 of tool input, 200000 in the output).\"",
+    },
+    output: {
+      value: 131072,
+      source: "vendor",
+      declaredAt: 32000,
+      measured: "2026-10-15",
+      samples: "nothing above 32000 watched on this route; that same refusal came back with the requested 200000 unclamped",
+      how: "Xiaomi's own entry for mimo-v2.6-flash, api.xiaomimimo.com and its China token plan, declares 1048576/131072, as do DeepInfra and nan; this route declares 32000 for the free id and states no completion ceiling of its own",
+    },
+  },
 };
 
 // "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 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.
+// 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/i;
 
 // Windows named by a refusal while this process is running, by model id. Not

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-zen-freex",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "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",