@alexeiled/claude-router 1.17.1 → 1.19.0
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/.claude-plugin/plugin.json +2 -2
- package/CHANGELOG.md +38 -0
- package/README.md +3 -0
- package/docs/architecture.md +1 -1
- package/docs/configuration.md +15 -4
- package/docs/evaluation.md +6 -2
- package/docs/native-router.md +1 -1
- package/docs/provider-experiments.md +141 -0
- package/docs/providers.md +83 -5
- package/docs/router-band.svg +9 -13
- package/docs/router-pane-now.svg +130 -120
- package/docs/router-pane-routes.svg +1 -1
- package/docs/router-pane-usage-whatif.svg +6 -8
- package/docs/router-pane-usage.svg +6 -8
- package/docs/routing-modes.md +3 -1
- package/docs/user-guide.md +12 -12
- package/hooks/native-router.mjs +33 -27
- package/lib/band.mjs +42 -37
- package/lib/display.mjs +47 -22
- package/lib/modes.mjs +3 -16
- package/lib/panel.mjs +82 -78
- package/lib/providers.mjs +88 -0
- package/lib/savings.mjs +5 -37
- package/lib/usage.mjs +29 -9
- package/lib/view.mjs +2 -4
- package/package.json +2 -2
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "router",
|
|
3
3
|
"displayName": "Router",
|
|
4
|
-
"version": "1.
|
|
5
|
-
"description": "Native model and effort routing within your provider. Anthropic, DeepSeek
|
|
4
|
+
"version": "1.19.0",
|
|
5
|
+
"description": "Native model and effort routing within your provider. Anthropic, DeepSeek, z.ai, MiniMax, MiMo and Kimi defaults, custom provider profiles, classifier advice and one model per subagent.",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Alexei Ledenev",
|
|
8
8
|
"url": "https://github.com/alexei-led"
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,43 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.19.0 (2026-10-31)
|
|
4
|
+
|
|
5
|
+
MiniMax, MiMo and Kimi gain built-in provider profiles alongside DeepSeek and z.ai.
|
|
6
|
+
|
|
7
|
+
### Added
|
|
8
|
+
|
|
9
|
+
- `minimax` defaults use MiniMax-M3.1-Flash with low, medium, high and max effort. Legacy M3 ignores effort and is not used as a deeper tier.
|
|
10
|
+
- `mimo` defaults combine MiMo-V2.6-Flash and Pro. The router selects models without claiming undocumented effort levels; provider-default thinking stays on.
|
|
11
|
+
- `kimi` defaults use Kimi-K3.1-Pro throughout the conversation, with low, high and max effort. They do not mix K2/K3 thinking histories.
|
|
12
|
+
- Each profile includes activity and subagent routes, image/context metadata, API list prices and conservative cache accounting. [Provider tables](docs/providers.md#new-provider-modes) show every cost, balanced and quality combination.
|
|
13
|
+
- [Research and experiments](docs/provider-experiments.md) record synthetic activity checks and native streaming tools. MiMo Flash's two format failures remain visible; no measured quality or savings guarantee is claimed.
|
|
14
|
+
|
|
15
|
+
### Fixed
|
|
16
|
+
|
|
17
|
+
- Cost mode skips unsupported effort levels when stepping down, rather than projecting back to the current level. Sparse ladders such as DeepSeek, z.ai and Kimi can now move max → high → low.
|
|
18
|
+
|
|
19
|
+
### Upgrade
|
|
20
|
+
|
|
21
|
+
- After upgrading, create `minimax-router.json`, `mimo-router.json` or `kimi-router.json` containing `{}` in the active Claude Code profile, then set `CLAUDE_ROUTER_PROVIDER` before launch. Missing or invalid files keep the native model unchanged.
|
|
22
|
+
- Start a fresh conversation when moving from another Kimi model to K3.1. Do not resume old model-specific thinking/tool history into it. Remove a fixed `CLAUDE_CODE_EFFORT_LEVEL` override to allow per-turn effort routing.
|
|
23
|
+
- Existing Anthropic users need no configuration change. Endpoint credentials and billing remain Claude Code's responsibility.
|
|
24
|
+
|
|
25
|
+
## 1.18.0 (2026-10-30)
|
|
26
|
+
|
|
27
|
+
The band and the pane now show one session cost readout: the same number, the same words, at the same moment.
|
|
28
|
+
|
|
29
|
+
### Changed
|
|
30
|
+
|
|
31
|
+
- The band's second row shows the answer and the parts that add up to it: `session routing +$0.18 (+4%) vs Opus 5.5 · high = −$0.42 cheaper models +$0.60 cache rebuilds · 34 replies`. Before, it showed `extra $0.18` beside only the largest cost (`cold-cache writes +$0.60`), which did not add up. On a narrow band the parts lose their words (`= −$0.42 + $0.60`), then the reply count drops, then the parts.
|
|
32
|
+
- The Now tab's SESSION block starts with the band's row and the ledger that adds up to it, with **Usage** beside it. When cache rebuilds cost more than the cheaper models saved, `▲ switches cost more than they saved` follows with **Policy**. The cost line at the end of the block is gone.
|
|
33
|
+
- One vocabulary everywhere: `routing −$x (−y%) vs <model>`, `cheaper models`, `stronger models`, `cache rebuilds`. The Usage tab, `/router`, TODAY and SUBAGENTS use it too. The policy's estimate for the switch it weighs is now `next switch ≈ $x`, so it no longer reads like the cache rebuilds already paid.
|
|
34
|
+
- After a `/model` change the band names the models the session's replies ran against, as the Usage tab does, instead of repricing the session against the new model.
|
|
35
|
+
|
|
36
|
+
### Fixed
|
|
37
|
+
|
|
38
|
+
- The pane counts the replies of the turn still running, marked `(N live)`. Before, it counted a turn only when the turn ended, so during a long turn the band showed a cost the pane did not have.
|
|
39
|
+
- The band's session readout no longer starts over when Claude Code restarts a resumed session: it reads the session's usage record, as the pane does.
|
|
40
|
+
|
|
3
41
|
## 1.17.1 (2026-10-28)
|
|
4
42
|
|
|
5
43
|
### Fixed
|
package/README.md
CHANGED
|
@@ -23,6 +23,9 @@ With `CLAUDE_CONFIG_DIR`, put the file in that directory instead.
|
|
|
23
23
|
| Anthropic, the default | `router.json` | Haiku 5.5, Sonnet 5.5, Opus 5.5 |
|
|
24
24
|
| `deepseek` | `deepseek-router.json` | DeepSeek Flash, routed by effort |
|
|
25
25
|
| `zai` | `zai-router.json` | GLM-5.3-Flash and GLM-5.3 |
|
|
26
|
+
| `minimax` | `minimax-router.json` | MiniMax-M3.1-Flash, routed by effort |
|
|
27
|
+
| `mimo` | `mimo-router.json` | MiMo-V2.6-Flash and MiMo-V2.6-Pro, no routed effort |
|
|
28
|
+
| `kimi` | `kimi-router.json` | Kimi-K3.1-Pro, routed by effort |
|
|
26
29
|
|
|
27
30
|
OpenRouter, Ollama, other local servers and other compatible hosted providers use custom `<provider>-router.json` files.
|
|
28
31
|
They have no built-in model defaults. A selected file must exist and validate, or the router leaves Claude Code's model unchanged.
|
package/docs/architecture.md
CHANGED
|
@@ -133,7 +133,7 @@ Nothing is recorded with `activityRouting: off`. Stats run inside a guard: a fai
|
|
|
133
133
|
|
|
134
134
|
### Routing vs your model
|
|
135
135
|
|
|
136
|
-
After each main reply, where the response is observed, `savings.mjs` prices the reply on the model that served it and the same tokens on "your model": the session's model and the effort Claude Code sent on the turn's first request. `compareModels` prices each reply against every model in `router.json` as "your model", at the session effort. Each keeps a simulated single cache in the loop under its models key in `yoursBy` (`{ total, at, onYours, model, effort }`), which a history reset clears; after an effort change the next reply finds it cold.
|
|
136
|
+
After each main reply, where the response is observed, `savings.mjs` prices the reply on the model that served it and the same tokens on "your model": the session's model and the effort Claude Code sent on the turn's first request. `compareModels` prices each reply against every model in `router.json` as "your model", at the session effort. Each keeps a simulated single cache in the loop under its models key in `yoursBy` (`{ total, at, onYours, model, effort }`), which a history reset clears; after an effort change the next reply finds it cold. Each reply also becomes a `replyEntry` in `usage.mjs`: its time, its cell `mode|activity|tier|modelId@effort` with the model that served it, its prices against the model selected then, its input, cache-read and output tokens, and what the same tokens cost on each model as yours. Models are kept by id, not by models key, because a key can later name another model. Until the turn ends its entries are also the view's `usageLive`; every readout (the two-row band, the Now and Usage tabs, `/router`) adds them to the record with `withReplies`, so they count the same replies at the same moment. At turn completion the entries leave `turnUsage` in the same tick they enter the held record, and every view write of the records carries `usageLive` with them, so a pane opened mid-write, a failed store write or a Reset counts a turn once or not at all, never twice. At turn completion `recordUsage` adds the turn's entries to the session's own `$.store` key `usage:v1:<session id>`, by local calendar day: per day the cells' nine sums, the what-if sums, the replies per your model, the routed cost per hour, the turns, and the route switches by tier and by activity, with `since`, the record's first write. Days older than 400 days leave the record when it is written. Each key has one writer, and Claude Code 2.1.296 writes one key under a file lock (observed in its code; the `$.store` types do not promise it), so sessions that finish turns at the same moment do not overwrite each other. The view's `usageStore` adds up two parts: every other session's key, read at session start and when the pane opens, and this session's record (`usageSession`), which the router reads once, holds in memory, adds each finished turn to and then writes, so a pane opened during that write counts the turn once. On that read, `prunedUsage` names other sessions' records with no day in the last 400 days and, past 1,000 records, those whose last day is oldest; a record that does not read whole, such as one a later version wrote, is never named. Each named record is read again and deleted only if it has not changed, so a session that wrote its record since keeps it; with no conditional delete in `$.store`, a write between that read and the delete is still lost. A day that does not read is dropped, and the others stay. The Usage tab sums the days of the chosen period (`summarize`); the period is kept across sessions in `usage:period`. Before these records each session kept undated totals in `savings:v1:<session id>`; they are no longer written, and the view's `savingsStore`, their sum, is added to the All period. **Delete history** first writes the time in `savings:reset:v1`, then deletes every usage, savings, activity stats, metrics and subagent record. A record whose first reply is older than that time reads as empty, and each session reads the time before it adds a turn, so a session that still holds its record from before a Reset in another session drops it instead of writing it back. The comparison is by milliseconds: a record whose first reply has the reset's millisecond, or one written while the clock had moved back, still counts. A stored value of any other shape reads as empty. A reply with routing off or after an engine fallback is not counted, but it still moves your model's cache. A reply whose cache lifetime cannot be read loses its prices only, and your model's cache still follows it; a usage without rate limits prices writes at five minutes. No failure here fails the turn. [Evaluation](evaluation.md#routing-vs-your-model) gives the method and its limits.
|
|
137
137
|
|
|
138
138
|
### Subagents
|
|
139
139
|
|
package/docs/configuration.md
CHANGED
|
@@ -39,18 +39,24 @@ A non-Anthropic file must exist and validate. It never falls back to `router.jso
|
|
|
39
39
|
|
|
40
40
|
### Provider prices
|
|
41
41
|
|
|
42
|
-
|
|
42
|
+
All non-Anthropic built-in model windows are at least 1M tokens.
|
|
43
43
|
Price estimates use the [DeepSeek peak API rates](https://api-docs.deepseek.com/quick_start/pricing) and [z.ai API list rates](https://docs.z.ai/guides/overview/pricing.md).
|
|
44
|
-
|
|
44
|
+
DeepSeek and z.ai rates were checked on 2026-10-28; the new provider rates on 2026-10-31.
|
|
45
45
|
|
|
46
46
|
| Model | Input / output / cached input, USD per million tokens |
|
|
47
47
|
| --- | --- |
|
|
48
48
|
| DeepSeek Flash | 0.30 / 1.20 / 0.006 |
|
|
49
49
|
| GLM-5.3-Flash | 0.15 / 0.50 / 0.03 |
|
|
50
50
|
| GLM-5.3 | 1.40 / 4.40 / 0.26 |
|
|
51
|
+
| MiniMax-M3.1-Flash | 0.15 / 0.60 / 0.015 |
|
|
52
|
+
| MiMo-V2.6-Flash | 0.14 / 0.28 / 0.0028 |
|
|
53
|
+
| MiMo-V2.6-Pro | 0.435 / 0.87 / 0.0036 |
|
|
54
|
+
| Kimi-K3.1-Pro | 2.00 / 10.00 / 0.20 |
|
|
51
55
|
|
|
52
56
|
These are fixed estimate inputs, not an invoice. DeepSeek off-peak rates differ, and z.ai plan quota uses its own multipliers.
|
|
53
|
-
|
|
57
|
+
New provider sources: [MiniMax pricing](https://platform.minimax.io/docs/pricing/overview),
|
|
58
|
+
[MiMo pricing](https://mimo.mi.com/docs/en-US/pricing), and [Kimi pricing](https://platform.kimi.ai/docs/pricing/chat).
|
|
59
|
+
All non-Anthropic built-in presets use `billing: "credits"`.
|
|
54
60
|
For an included-plan model, set `billing: "plan"` to disable the cold-input cash cap.
|
|
55
61
|
A provider name or URL does not establish its billing product.
|
|
56
62
|
|
|
@@ -61,7 +67,7 @@ A provider name or URL does not establish its billing product.
|
|
|
61
67
|
| Mode | Use | Estimate |
|
|
62
68
|
| --- | --- | --- |
|
|
63
69
|
| `explicit` | Anthropic default | Configured write multipliers and TTLs |
|
|
64
|
-
| `automatic` |
|
|
70
|
+
| `automatic` | All other built-in profiles and custom-profile default | Reported hit/miss input rates, no separate write premium |
|
|
65
71
|
| `disabled` | No cache discount to model | All input at the uncached rate, never marked warm |
|
|
66
72
|
|
|
67
73
|
Automatic-cache bounds allow a future hit or a full miss, including after an observed miss.
|
|
@@ -83,6 +89,11 @@ An unknown cache state is not proof of a miss.
|
|
|
83
89
|
|
|
84
90
|
[DeepSeek caching](https://api-docs.deepseek.com/guides/kv_cache) is automatic and best-effort. Its Anthropic endpoint ignores explicit cache controls.
|
|
85
91
|
[z.ai caching](https://docs.z.ai/guides/capabilities/cache.md) has no verified model-specific TTL.
|
|
92
|
+
MiniMax and MiMo expose automatic prefix caching; no retention guarantee is assumed here.
|
|
93
|
+
Kimi's default five-minute cache fills cost the ordinary input rate; the preset does not select top-level one-hour
|
|
94
|
+
cache control, whose writes cost twice as much. Its observed default fills/reads are priced, but TTL is not used
|
|
95
|
+
to promise future hits. A custom client that selects one-hour Kimi caching must configure its write premium.
|
|
96
|
+
MiMo's currently free cache-write promotion is not treated as free cold input.
|
|
86
97
|
Claude Code's `DISABLE_PROMPT_CACHING` does not establish whether an automatic server cache is disabled.
|
|
87
98
|
|
|
88
99
|
Valid observed usage can still be priced for activity statistics.
|
package/docs/evaluation.md
CHANGED
|
@@ -21,6 +21,10 @@ Terminal engineering and SRE results differ. Neither GLM model leads every activ
|
|
|
21
21
|
Measured max-effort results do not establish low/high performance or an optimal routing matrix.
|
|
22
22
|
The original DeepSeek benchmark profile does not establish the quality of its newer hosted 1017 snapshot.
|
|
23
23
|
|
|
24
|
+
MiniMax, MiMo and Kimi have [separate sourced research and live checks](provider-experiments.md), including
|
|
25
|
+
all activity/mode routes, retained output-format failures and native streaming tool continuations.
|
|
26
|
+
Those small synthetic checks do not establish repository-quality rankings or optimal efforts.
|
|
27
|
+
|
|
24
28
|
### Compatibility checks
|
|
25
29
|
|
|
26
30
|
On 2026-10-28, six synthetic live requests per provider returned HTTP 200.
|
|
@@ -153,13 +157,13 @@ The Usage tab compares what routed replies cost with what the same tokens would
|
|
|
153
157
|
Method, per main reply that routing chose:
|
|
154
158
|
|
|
155
159
|
- **Routed** prices the usage Claude reported (uncached input, cache read, cache write, output) on the model that served it.
|
|
156
|
-
- **Yours** prices the same tokens on each model in `router.json` at the session effort. The Usage tab keeps each reply against the model selected when it ran, and **What if** shows the period against each model alone; the two-row band and `/router` show the session
|
|
160
|
+
- **Yours** prices the same tokens on each model in `router.json` at the session effort. The Usage tab keeps each reply against the model selected when it ran, and **What if** shows the period against each model alone; the two-row band, the Now tab and `/router` show the same session readout, the running turn's replies included. While this reply and the one before it ran on that model's route, it is the reply's own usage, so a session on your model differs by exactly $0.00. Otherwise each model keeps one cache that never switched: it reads the previous prompt, up to this one less its uncached input, inside the cache lifetime, unless a compaction shrank the history or, on a model that keeps one cache per effort, the effort changed since, and never less than the API actually read; it writes the rest. Output tokens are the same.
|
|
157
161
|
- **Parts**: the served model on your cache against yours is the model price, under cheaper models when negative and stronger than yours when positive; routed against the served model on your cache is the cache the switches cost, never negative. They sum to the difference. The pane rounds to cents and gives the remainder only to a part that is not zero: a surplus to the switch part, else the stronger part, else the cheaper part toward $0.00; a shortfall comes off the stronger part, down to $0.00, then the cheaper part. The shown parts add up, none changes sign, and none appears from rounding alone.
|
|
158
162
|
- **Prices**: `router.json` list prices through `ratesAt`, so Haiku 5.5 above 100,000 prompt tokens is priced at 5x. Claude Code reports no 5m/1h split to a Mod, so cache writes use the lifetime Claude Code 2.1.296 gives the main conversation by its own rule: one hour on a Claude plan unless an environment variable or the `promptCacheTtl` setting says otherwise, five minutes with an API key.
|
|
159
163
|
|
|
160
164
|
Checks:
|
|
161
165
|
|
|
162
|
-
- Unit tests (`test/savings.test.mjs`) cover a session that saves, one that costs more with Haiku as your model, equal routes at exactly 0, cache expiry at 5m and 1h, a compaction, a change of your model or effort, the 100K surcharge, an unpriced model, and a corrupted store. `test/hook-routing.test.mjs` covers two sessions finishing turns at the same moment,
|
|
166
|
+
- Unit tests (`test/savings.test.mjs`) cover a session that saves, one that costs more with Haiku as your model, equal routes at exactly 0, cache expiry at 5m and 1h, a compaction, a change of your model or effort, the 100K surcharge, an unpriced model, and a corrupted store. `test/hook-routing.test.mjs` covers two sessions finishing turns at the same moment, a `/model` change mid-session that keeps each reply against its own model, and a running turn's replies counted once before and after the turn is recorded. `test/usage.test.mjs` covers calendar days across month ends and daylight saving changes, the periods, the record cap and expiry, the trend buckets and what is worth a look; `test/usage-view.test.mjs` covers the Usage tab.
|
|
163
167
|
- A one-off replay, not checked in, of this machine's main-conversation transcripts from 2026-10-01 to 2026-10-10 (nine sessions with 10 or more replies) gave $0.00 for every session that ran only on the model it was compared with: three on Opus 5.5, one on Haiku 5.5. Every main-conversation cache write in them was a one-hour write, which is what the lifetime rule gives on this Max plan.
|
|
164
168
|
- A live Claude Code 2.1.296 session on 2026-10-10, Opus 5.5 at `high` with turns pinned to Haiku 5.5, showed **Routed replies $0.48** beside **Cost $0.480 reported by Claude** for the same 16 replies; its last Haiku reply had a 114K-token prompt, which agrees only at the 5x rate. A Haiku 5.5 session with a pinned Opus turn showed $0.45 routed against $0.446 reported.
|
|
165
169
|
|
package/docs/native-router.md
CHANGED
|
@@ -39,7 +39,7 @@ The status band is one line above the prompt: a tier meter, the activity, the ro
|
|
|
39
39
|
| Classifier support | Per-tier probabilities from the last classification; under **Why**, the support for the switch against the bar the policy required, and the switch cost. Pins and skipped calls leave it empty. |
|
|
40
40
|
| Activity | The classifier's activity choice as a verb with its share, the two next-best answers, and the threshold at which an activity applies; `uncertain` shown dim. Empty with routing off, a pin, or no answer. |
|
|
41
41
|
| Session and today (Now) | Every main-conversation reply since Claude Code started the session as a strip colored by tier, pairs of cells merging past 48 cells or on a narrow pane; a dot where the router did not serve, and `since HH:MM` once a restart started the strip again. The replies per tier and per activity, the route switches and the last one, and routing against your model for the session and, once another session added to it, for today; today's first finding worth a look. |
|
|
42
|
-
| Routing vs your model (Usage) | For a period (this session, today, 7 or 30 days, this month, or all), routed replies at configured list prices against the same tokens on your model, the model `/model` selected at the session effort when each reply ran: a ledger from your model through cheaper models, stronger models and
|
|
42
|
+
| Routing vs your model (Usage) | For a period (this session, today, 7 or 30 days, this month, or all), routed replies at configured list prices against the same tokens on your model, the model `/model` selected at the session effort when each reply ran: a ledger from your model through cheaper models, stronger models and cache rebuilds to routed. The two-row band and the Now tab's SESSION block show the session's answer and parts in the same words, the running turn's replies included; tokens and cache hit. `early sample` below 10 replies. Output length is held the same; answer quality is not measured. |
|
|
43
43
|
| Breakdown (Usage) | The period's replies, cost and difference against your model by activity, model or tier, each row opening to its routes or activities; the cost per hour, day or week, or **What if**, the same tokens on each model alone; from 20 replies, the cells worth a look, linked to Routes or Policy. |
|
|
44
44
|
| Across sessions (Classifier) | The counts kept since the last reset: labelled turns, tool agreement on the classifier's raw answer, overall and for `code`, `ops` and `explore`, the two largest mismatches, activity moves inside a tier taken and refused, and escalations after a cheaper activity move. The active classifier's p95 latency shows on its **Deadline** line. `/router` text shows the agreement. |
|
|
45
45
|
| Cost | Claude Code's native usage value. A plan's list-price estimates are not subscription cash charges. |
|
|
@@ -0,0 +1,141 @@
|
|
|
1
|
+
# MiniMax, MiMo and Kimi evidence
|
|
2
|
+
|
|
3
|
+
Checked 2026-10-31. The [default routes](providers.md#built-in-defaults) are conservative starting policies,
|
|
4
|
+
not an optimal activity matrix or measured savings. These execution providers are separate from the classifier.
|
|
5
|
+
|
|
6
|
+
## Contracts and selection
|
|
7
|
+
|
|
8
|
+
| Provider | Selected model(s) | Documented controls used | Why |
|
|
9
|
+
| --- | --- | --- | --- |
|
|
10
|
+
| MiniMax | MiniMax-M3.1-Flash | low, medium, high, max | Current effort-capable model; cheaper than M3. M3 ignores effort. |
|
|
11
|
+
| MiMo | MiMo-V2.6-Flash / Pro | No routed effort | Flash for volume, Pro for harder work. Anthropic docs establish binary thinking, not depth levels. |
|
|
12
|
+
| Kimi | Kimi-K3.1-Pro | low, high, max | Cheaper successor to K3; one model avoids mixing preserved-thinking histories. |
|
|
13
|
+
|
|
14
|
+
MiniMax also documents `xhigh`, but some Claude Code versions serialize it as `high`. The preset omits it
|
|
15
|
+
rather than claim an extra distinct compute setting. Raw `xhigh` acceptance was checked, not native normalization.
|
|
16
|
+
Kimi K2.7 is not used as a cheap tier: its lifecycle notice closes access for new users on 2026-10-31
|
|
17
|
+
and plans retirement by the end of December 2026. Existing K3 users must start a fresh conversation to migrate to K3.1.
|
|
18
|
+
|
|
19
|
+
The local model-cards catalog was an initial reference: MiniMax M3 verified 2026-07-14 and Kimi K3/K2.7
|
|
20
|
+
verified 2026-09-13. It has no M3.1 Flash, K3.1 or MiMo record. Current official endpoint docs supersede
|
|
21
|
+
older catalog controls and K2 context claims.
|
|
22
|
+
|
|
23
|
+
### Primary sources
|
|
24
|
+
|
|
25
|
+
- MiniMax [Messages](https://platform.minimax.io/docs/api-reference/text-chat-anthropic),
|
|
26
|
+
[SDK compatibility](https://platform.minimax.io/docs/api-reference/text-anthropic-api),
|
|
27
|
+
[pricing](https://platform.minimax.io/docs/pricing/overview),
|
|
28
|
+
[automatic caching](https://platform.minimax.io/docs/api-reference/text-prompt-caching),
|
|
29
|
+
[Claude Code](https://platform.minimax.io/docs/m-plan/claude-code),
|
|
30
|
+
[Flash release](https://www.minimax.io/blog/minimax-m31f).
|
|
31
|
+
- MiMo [Anthropic API](https://mimo.mi.com/docs/en-US/api/chat/anthropic-api),
|
|
32
|
+
[model selection](https://mimo.mi.com/docs/quick-start/summary/model),
|
|
33
|
+
[pricing](https://mimo.mi.com/docs/en-US/pricing),
|
|
34
|
+
[Claude Code](https://mimo.mi.com/docs/integration/claudecode),
|
|
35
|
+
[deep thinking](https://mimo.mi.com/docs/en-US/quick-start/usage-guide/text-generation/deep-thinking).
|
|
36
|
+
- Kimi [Messages](https://platform.kimi.ai/docs/api/messages),
|
|
37
|
+
[models and lifecycle](https://platform.kimi.ai/docs/models),
|
|
38
|
+
[K3.1 guide](https://platform.kimi.ai/docs/guide/kimi-k3-1-pro-quickstart),
|
|
39
|
+
[pricing](https://platform.kimi.ai/docs/pricing/chat),
|
|
40
|
+
[caching](https://platform.kimi.ai/docs/guide/context-caching),
|
|
41
|
+
[K3 session guidance](https://forum.moonshot.ai/t/kimi-k3-is-here-our-most-capable-model/480).
|
|
42
|
+
|
|
43
|
+
Vendor results motivate the model choices, not the exact activity overrides. No independent head-to-head
|
|
44
|
+
repository benchmark establishes which effort each activity needs. Token prices are not prices per successful task.
|
|
45
|
+
|
|
46
|
+
## Live checks
|
|
47
|
+
|
|
48
|
+
All prompts and fixtures were synthetic. No real repository code, private conversations or credentials
|
|
49
|
+
are included in artifacts. Credential files stay local. JSON checks save final answers and usage, never reasoning text.
|
|
50
|
+
|
|
51
|
+
### Raw controls
|
|
52
|
+
|
|
53
|
+
[`provider-controls.json`](../experiments/mod-router/results/provider-controls.json) records 20 HTTP 200 requests:
|
|
54
|
+
old/new MiniMax, both MiMo models, and old/new Kimi. The body used a prime-number JSON prompt,
|
|
55
|
+
`max_tokens: 2048`, `thinking: {type: "adaptive"}`, and the recorded `output_config.effort`.
|
|
56
|
+
All responses named the requested model.
|
|
57
|
+
|
|
58
|
+
HTTP acceptance alone cannot distinguish honored fields from ignored fields. In particular, M3 success does not
|
|
59
|
+
make it effort-controllable, and MiMo low/high/max success does not establish different reasoning depths.
|
|
60
|
+
The production MiMo preset therefore lists no effort levels. Xiaomi's documented default thinking remains on;
|
|
61
|
+
Claude Code may still send its session effort and adaptive thinking, accepted in the native smoke test.
|
|
62
|
+
|
|
63
|
+
### Activity and mode microchecks
|
|
64
|
+
|
|
65
|
+
`node scripts/probe-provider-routes.mjs <provider> <budget-usd>` is billed and opt-in.
|
|
66
|
+
It asks one deterministic JSON task for each distinct activity/model/effort route across all tiers and modes,
|
|
67
|
+
using [the checked-in tasks](../test/fixtures/provider-tasks.json). Every mode/tier cell references its measured route.
|
|
68
|
+
The tests check small code-contract outputs, a boundary bug, an import graph, topological planning, SQL injection,
|
|
69
|
+
replica status and a configuration reference. They are **not code editing or repository-quality benchmarks**.
|
|
70
|
+
|
|
71
|
+
| Provider | Distinct calls | Exact JSON checks passed | Estimated API-list cost |
|
|
72
|
+
| --- | ---: | ---: | ---: |
|
|
73
|
+
| MiniMax | 28 | 28 | $0.001472 |
|
|
74
|
+
| MiMo | 14 | 12 | $0.001001 |
|
|
75
|
+
| Kimi | 21 | 21 | $0.024376 |
|
|
76
|
+
|
|
77
|
+
Results: [MiniMax](../experiments/mod-router/results/provider-routes-minimax.json),
|
|
78
|
+
[MiMo](../experiments/mod-router/results/provider-routes-mimo.json),
|
|
79
|
+
[Kimi](../experiments/mod-router/results/provider-routes-kimi.json).
|
|
80
|
+
|
|
81
|
+
MiMo Flash returned objects instead of module-name strings for `explore`, and added prose to an otherwise correct
|
|
82
|
+
`plan` array. Those are retained failures, not retried or hidden by a permissive parser. Pro passed both.
|
|
83
|
+
One sample does not justify moving every exploration or planning task to Pro.
|
|
84
|
+
MiniMax/Kimi low effort also passed these easy tasks, so the sample does not prove high/max necessary for harder work.
|
|
85
|
+
|
|
86
|
+
### Native streaming and tools
|
|
87
|
+
|
|
88
|
+
Claude Code **2.1.316** loaded the production Mod in isolated homes. Each provider ran a pinned high turn,
|
|
89
|
+
a Read tool continuation, a pinned micro turn, and another Read continuation: four upstream requests.
|
|
90
|
+
The test forwarded only these synthetic requests to fixed provider endpoints, capped output at 2,048 tokens,
|
|
91
|
+
and verified the requested/served model, supported routed effort and final marker.
|
|
92
|
+
|
|
93
|
+
| Provider | Observed transition | Result |
|
|
94
|
+
| --- | --- | --- |
|
|
95
|
+
| MiniMax | M3.1 Flash max → low | Passed |
|
|
96
|
+
| MiMo | Pro → Flash, session effort retained | Passed |
|
|
97
|
+
| Kimi | K3.1 Pro max → low, same model | Passed |
|
|
98
|
+
|
|
99
|
+
Artifacts: [MiniMax](../experiments/mod-router/results/provider-native-minimax.json),
|
|
100
|
+
[MiMo](../experiments/mod-router/results/provider-native-mimo.json),
|
|
101
|
+
[Kimi](../experiments/mod-router/results/provider-native-kimi.json).
|
|
102
|
+
Repeat with `node experiments/mod-router/scripts/provider-live.mjs <provider> <budget-usd>` (billed).
|
|
103
|
+
This temporary diagnostic forwarder is **not** part of the shipped router.
|
|
104
|
+
|
|
105
|
+
All three reported positive cache reads on tool continuations. MiniMax/MiMo streamed usage omitted cache-creation
|
|
106
|
+
counts; the engine compatibility check covers omitted-counter normalization. Kimi reported ordinary-price five-minute
|
|
107
|
+
cache fills and cache reads; the native request contained no top-level one-hour cache control.
|
|
108
|
+
No cross-effort hit-rate or TTL guarantee follows from these few requests.
|
|
109
|
+
|
|
110
|
+
The operator approved a $5 ceiling. Raw controls, microchecks and two native smoke passes together accounted for
|
|
111
|
+
approximately **$0.0625** at published list prices, including the superseded first native pass.
|
|
112
|
+
The [spend record](../experiments/mod-router/results/provider-experiment-spend.json) includes the superseded pass's
|
|
113
|
+
captured console totals so the aggregate can be reproduced. This is not a provider invoice or subscription-quota estimate.
|
|
114
|
+
The scripts enforce **per-invocation** ceilings only; the supervisor tracked the aggregate manually, not with a shared
|
|
115
|
+
runtime ledger. Each repeat needs a fresh spending authorization.
|
|
116
|
+
|
|
117
|
+
## Offline checks
|
|
118
|
+
|
|
119
|
+
`npm run test:providers` uses Claude Code and a loopback-only API with dummy credentials, not paid calls.
|
|
120
|
+
It covers all five non-Anthropic built-ins, profile selection, high/micro transitions, tools, omitted usage,
|
|
121
|
+
missing files and invalid configuration. Unit tests cover every new tier × activity × mode, pinning,
|
|
122
|
+
file isolation, reset/undo, metadata, lack of MiMo effort controls and the single-model Kimi catalog.
|
|
123
|
+
The tables in [Providers](providers.md#new-provider-modes) are generated and checked against the actual route transform.
|
|
124
|
+
|
|
125
|
+
Cost mode now steps to the next supported lower effort, skipping gaps: `max → high → low` on Kimi,
|
|
126
|
+
DeepSeek and z.ai. Previously upward projection could return the original effort and make cost mode a no-op.
|
|
127
|
+
MiMo has no effort lever; adjacent equal routes intentionally remain equal.
|
|
128
|
+
|
|
129
|
+
## Limits and upgrade triggers
|
|
130
|
+
|
|
131
|
+
Not tested: native images/video, near-1M context, compaction or rewind with provider thinking signatures,
|
|
132
|
+
forced tool choice, sustained rate limits, subscription eligibility, or real per-activity task quality and savings.
|
|
133
|
+
Raw API vision support is documented, not an end-to-end screenshot result.
|
|
134
|
+
|
|
135
|
+
MiMo Token Plan terms restrict general API/backend automation; use the documented PAYG endpoint and prices
|
|
136
|
+
for these experiments. A Claude Code integration does not establish that every non-coding automation qualifies
|
|
137
|
+
for a subscription. Check your plan terms and endpoint separately.
|
|
138
|
+
|
|
139
|
+
Keep these small presets until a representative coding/debug/review workload measures task success, retries,
|
|
140
|
+
total input/output, latency and cost per accepted change. Expand activity overrides only when that evidence
|
|
141
|
+
supports a difference. Do not add K2/K3 mixing or unsupported effort controls to make the tables look richer.
|
package/docs/providers.md
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
Claude Router routes models and effort within the provider that Claude Code already uses.
|
|
4
4
|
Set a provider name and give the router a matching JSON file. No provider-specific plugin or proxy is needed.
|
|
5
5
|
|
|
6
|
-
**Built-in profiles:** Anthropic, DeepSeek
|
|
6
|
+
**Built-in profiles:** Anthropic, DeepSeek, z.ai, MiniMax, MiMo and Kimi.
|
|
7
7
|
**Custom profiles:** OpenRouter, Ollama, other local servers, and other hosted providers with a Claude Code-compatible Anthropic endpoint.
|
|
8
8
|
Custom profiles need their own model settings. They do not inherit Claude models.
|
|
9
9
|
|
|
@@ -42,12 +42,15 @@ The directory is `CLAUDE_CONFIG_DIR` when set, otherwise `~/.claude`.
|
|
|
42
42
|
| Unset, empty, or `anthropic` | `router.json` | Haiku 5.5, Sonnet 5.5, Opus 5.5 |
|
|
43
43
|
| `deepseek` | `deepseek-router.json` | DeepSeek Flash |
|
|
44
44
|
| `zai` | `zai-router.json` | GLM-5.3-Flash, GLM-5.3 |
|
|
45
|
+
| `minimax` | `minimax-router.json` | MiniMax-M3.1-Flash |
|
|
46
|
+
| `mimo` | `mimo-router.json` | MiMo-V2.6-Flash, MiMo-V2.6-Pro |
|
|
47
|
+
| `kimi` | `kimi-router.json` | Kimi-K3.1-Pro |
|
|
45
48
|
| `openrouter` | `openrouter-router.json` | None. Supply a complete profile. |
|
|
46
49
|
| `ollama` | `ollama-router.json` | None. Supply a complete profile. |
|
|
47
50
|
| Any other valid name | `<provider>-router.json` | None. Supply a complete profile. |
|
|
48
51
|
|
|
49
52
|
Names are local profile identifiers, not a provider registry or an endpoint lookup.
|
|
50
|
-
For example, `
|
|
53
|
+
For example, `local` or `my-gateway` can name a custom profile.
|
|
51
54
|
Names must start with a lowercase letter, contain only lowercase letters, digits and hyphens, and have at most 64 characters.
|
|
52
55
|
|
|
53
56
|
**Setting the name does not change Claude Code's endpoint, credentials or billing product.**
|
|
@@ -68,8 +71,20 @@ For an all-local setup, [configure the Ollama classifier](user-guide.md#use-olla
|
|
|
68
71
|
## Built-in defaults
|
|
69
72
|
|
|
70
73
|
Anthropic is the default when no provider name is set.
|
|
71
|
-
|
|
72
|
-
A file containing `{}` is enough
|
|
74
|
+
Every non-Anthropic built-in requires its named file, even when you want only defaults.
|
|
75
|
+
A file containing `{}` is enough. MiniMax, MiMo and Kimi require Router 1.19.0 or newer.
|
|
76
|
+
|
|
77
|
+
```sh
|
|
78
|
+
# First create the selected profile file containing {}, then launch on a configured model:
|
|
79
|
+
CLAUDE_ROUTER_PROVIDER=minimax claude --model 'MiniMax-M3.1-Flash[1m]'
|
|
80
|
+
CLAUDE_ROUTER_PROVIDER=mimo claude --model 'mimo-v2.6-flash[1m]'
|
|
81
|
+
CLAUDE_ROUTER_PROVIDER=kimi claude --model 'kimi-k3.1-pro[1m]'
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
Remove a fixed `CLAUDE_CODE_EFFORT_LEVEL` override if you want the router's per-turn efforts.
|
|
85
|
+
When migrating Kimi, start a **fresh conversation**. Its preserved thinking/signatures are model-specific;
|
|
86
|
+
resuming another model's history into K3-family models is not a supported migration.
|
|
87
|
+
The default Kimi ladder uses one model throughout, not a K2/K3 mixture.
|
|
73
88
|
|
|
74
89
|
### Model IDs
|
|
75
90
|
|
|
@@ -81,6 +96,10 @@ A file containing `{}` is enough for either.
|
|
|
81
96
|
| DeepSeek | `flash` | `deepseek-flash[1m]` |
|
|
82
97
|
| z.ai | `flash` | `glm-5.3-flash[1m]` |
|
|
83
98
|
| z.ai | `glm` | `glm-5.3[1m]` |
|
|
99
|
+
| MiniMax | `flash` | `MiniMax-M3.1-Flash[1m]` |
|
|
100
|
+
| MiMo | `flash` | `mimo-v2.6-flash[1m]` |
|
|
101
|
+
| MiMo | `pro` | `mimo-v2.6-pro[1m]` |
|
|
102
|
+
| Kimi | `k3` | `kimi-k3.1-pro[1m]` |
|
|
84
103
|
|
|
85
104
|
`[1m]` is a Claude Code context hint, not a different served model.
|
|
86
105
|
Changing Claude Code's model-slot environment variables does not update this catalog.
|
|
@@ -95,8 +114,13 @@ Each cell is `model alias · effort`. All profiles start at tier `low`.
|
|
|
95
114
|
| Anthropic | haiku · medium | haiku · high | opus · medium | opus · xhigh |
|
|
96
115
|
| DeepSeek | flash · low | flash · high | flash · high | flash · max |
|
|
97
116
|
| z.ai | flash · low | flash · high | glm · high | glm · max |
|
|
117
|
+
| MiniMax | flash · low | flash · medium | flash · high | flash · max |
|
|
118
|
+
| MiMo | flash · none | flash · none | pro · none | pro · none |
|
|
119
|
+
| Kimi | k3 · low | k3 · high | k3 · high | k3 · max |
|
|
98
120
|
|
|
99
121
|
A provider can use one model at several efforts. Two tiers can also share the same model and effort.
|
|
122
|
+
`none` for MiMo means **no routed effort**, not thinking off. Claude Code may still send its session effort;
|
|
123
|
+
Xiaomi does not document granular reasoning levels for its Anthropic endpoint. The preset lists `efforts: []`.
|
|
100
124
|
|
|
101
125
|
### Activity overrides
|
|
102
126
|
|
|
@@ -110,9 +134,13 @@ With activity routing on, these cells replace the base route. Other cells keep t
|
|
|
110
134
|
| z.ai | `code`, `debug`, `plan`, `review` | `medium` | glm · max |
|
|
111
135
|
| z.ai | `ops`, `explore`, `docs` | `medium` | flash · high |
|
|
112
136
|
| z.ai | `ops`, `explore`, `docs` | `high` | flash · max |
|
|
137
|
+
| MiniMax | `code`, `debug`, `plan`, `review` | `medium` | flash · max |
|
|
138
|
+
| MiMo | `ops`, `explore`, `docs` | `medium` | flash · none |
|
|
139
|
+
| Kimi | `code`, `debug`, `plan`, `review` | `medium` | k3 · max |
|
|
113
140
|
|
|
114
141
|
GLM-5.3 is text-only. Image-bearing history excludes it when the router can select a compatible route.
|
|
115
|
-
The default models all have a
|
|
142
|
+
The default models all have a context window of at least 1M tokens.
|
|
143
|
+
The four new model entries support image input at the provider; native image and near-limit context paths have not been tested.
|
|
116
144
|
|
|
117
145
|
Subagent routing is on for built-in profiles:
|
|
118
146
|
|
|
@@ -121,6 +149,9 @@ Subagent routing is on for built-in profiles:
|
|
|
121
149
|
| Anthropic | haiku | sonnet | opus |
|
|
122
150
|
| DeepSeek | flash | flash | flash |
|
|
123
151
|
| z.ai | flash | glm | glm |
|
|
152
|
+
| MiniMax | flash | flash | flash |
|
|
153
|
+
| MiMo | flash | pro | pro |
|
|
154
|
+
| Kimi | k3 | k3 | k3 |
|
|
124
155
|
|
|
125
156
|
Subagents receive a model at spawn, not a routed effort. Their own effort setting still applies.
|
|
126
157
|
|
|
@@ -128,6 +159,53 @@ These defaults are starting policies, not measured quality or savings guarantees
|
|
|
128
159
|
See [the evidence and limits](evaluation.md#provider-profiles).
|
|
129
160
|
For prices and cache settings, see [the configuration reference](configuration.md#provider-profiles).
|
|
130
161
|
|
|
162
|
+
## New provider modes
|
|
163
|
+
|
|
164
|
+
These are configured routes by tier and activity, before vote, context, failure, dwell and cache-cost guards.
|
|
165
|
+
`base/uncertain` means the tier's base route; an uncertain classifier tier keeps the incumbent tier.
|
|
166
|
+
A pin bypasses modes and activities. The ordinary [mode rules](routing-modes.md) apply without provider-specific code.
|
|
167
|
+
Generate these tables with `node scripts/provider-matrix.mjs`.
|
|
168
|
+
|
|
169
|
+
<!-- provider-matrix:start -->
|
|
170
|
+
**minimax**
|
|
171
|
+
|
|
172
|
+
| Tier | Activities | cost | balanced | quality |
|
|
173
|
+
| --- | --- | --- | --- | --- |
|
|
174
|
+
| micro | base/uncertain, code, debug, explore, plan, review, ops, docs | flash · low | flash · low | flash · low |
|
|
175
|
+
| low | base/uncertain, code, debug, explore, plan, review, ops, docs | flash · low | flash · medium | flash · high |
|
|
176
|
+
| medium | base/uncertain, explore, ops, docs | flash · medium | flash · high | flash · max |
|
|
177
|
+
| medium | code, debug, plan, review | flash · high | flash · max | flash · max |
|
|
178
|
+
| high | base/uncertain, code, debug, explore, plan, review, ops, docs | flash · high | flash · max | flash · max |
|
|
179
|
+
|
|
180
|
+
**mimo**
|
|
181
|
+
|
|
182
|
+
| Tier | Activities | cost | balanced | quality |
|
|
183
|
+
| --- | --- | --- | --- | --- |
|
|
184
|
+
| micro | base/uncertain, code, debug, explore, plan, review, ops, docs | flash · no routed effort | flash · no routed effort | flash · no routed effort |
|
|
185
|
+
| low | base/uncertain, code, debug, plan, review | flash · no routed effort | flash · no routed effort | pro · no routed effort |
|
|
186
|
+
| low | explore, ops, docs | flash · no routed effort | flash · no routed effort | flash · no routed effort |
|
|
187
|
+
| medium | base/uncertain, code, debug, plan, review | flash · no routed effort | pro · no routed effort | pro · no routed effort |
|
|
188
|
+
| medium | explore, ops, docs | flash · no routed effort | flash · no routed effort | pro · no routed effort |
|
|
189
|
+
| high | base/uncertain, code, debug, plan, review | pro · no routed effort | pro · no routed effort | pro · no routed effort |
|
|
190
|
+
| high | explore, ops, docs | flash · no routed effort | pro · no routed effort | pro · no routed effort |
|
|
191
|
+
|
|
192
|
+
**kimi**
|
|
193
|
+
|
|
194
|
+
| Tier | Activities | cost | balanced | quality |
|
|
195
|
+
| --- | --- | --- | --- | --- |
|
|
196
|
+
| micro | base/uncertain, code, debug, explore, plan, review, ops, docs | k3 · low | k3 · low | k3 · low |
|
|
197
|
+
| low | base/uncertain, code, debug, explore, plan, review, ops, docs | k3 · low | k3 · high | k3 · max |
|
|
198
|
+
| medium | base/uncertain, explore, ops, docs | k3 · low | k3 · high | k3 · max |
|
|
199
|
+
| medium | code, debug, plan, review | k3 · high | k3 · max | k3 · max |
|
|
200
|
+
| high | base/uncertain, code, debug, explore, plan, review, ops, docs | k3 · high | k3 · max | k3 · max |
|
|
201
|
+
<!-- provider-matrix:end -->
|
|
202
|
+
|
|
203
|
+
MiniMax uses all four preset effort levels. `xhigh` is omitted because some Claude Code versions send it as `high`;
|
|
204
|
+
`max` supplies the deeper setting. Legacy M3 ignores effort and is not a stronger tier by default.
|
|
205
|
+
MiMo's cost/quality modes change models where a neighbouring tier permits it; otherwise the route stays the same.
|
|
206
|
+
Kimi uses only `low`, `high`, `max`, the documented controls, and never promotes a session into another model.
|
|
207
|
+
These are starting policies, not an optimal activity matrix. See [research and experiments](provider-experiments.md).
|
|
208
|
+
|
|
131
209
|
## Add another provider
|
|
132
210
|
|
|
133
211
|
No code change or provider registration is needed.
|
package/docs/router-band.svg
CHANGED
|
@@ -47,12 +47,10 @@
|
|
|
47
47
|
<text x="765.0" y="121" fill="#87d787" xml:space="preserve">100%</text>
|
|
48
48
|
<text x="811.8" y="121" fill="#d0d0d0" xml:space="preserve">Router</text>
|
|
49
49
|
<text x="24.0" y="140" fill="#7c7c7c" xml:space="preserve">session </text>
|
|
50
|
-
<text x="94.2" y="140" fill="#6fcf97" font-weight="700" xml:space="preserve">
|
|
51
|
-
<text x="
|
|
52
|
-
<text x="
|
|
53
|
-
<text x="
|
|
54
|
-
<text x="499.8" y="140" fill="#7c7c7c" xml:space="preserve"> · </text>
|
|
55
|
-
<text x="538.8" y="140" fill="#7c7c7c" xml:space="preserve">cold-cache writes +$0.47</text>
|
|
50
|
+
<text x="94.2" y="140" fill="#6fcf97" font-weight="700" xml:space="preserve">routing −$1.84 (−22%)</text>
|
|
51
|
+
<text x="258.0" y="140" fill="#d0d0d0" xml:space="preserve"> vs Opus 5.5 · xhigh</text>
|
|
52
|
+
<text x="414.0" y="140" fill="#7c7c7c" xml:space="preserve"> = −$2.31 + $0.47</text>
|
|
53
|
+
<text x="562.2" y="140" fill="#7c7c7c" xml:space="preserve"> · 64 replies</text>
|
|
56
54
|
<text x="24.0" y="159" fill="#7c7c7c" xml:space="preserve">pin next turn </text>
|
|
57
55
|
<rect x="133.2" y="145" width="70.2" height="18" rx="4" fill="#2e3340"/>
|
|
58
56
|
<text x="133.2" y="159" fill="#d0d0d0" xml:space="preserve">[ micro ]</text>
|
|
@@ -150,11 +148,9 @@
|
|
|
150
148
|
<text x="297.0" y="484" fill="#7c7c7c" xml:space="preserve"> · </text>
|
|
151
149
|
<text x="336.0" y="484" fill="#7c7c7c" xml:space="preserve">= fits</text>
|
|
152
150
|
<text x="382.8" y="484" fill="#7c7c7c" xml:space="preserve"> · </text>
|
|
153
|
-
<text x="421.8" y="484" fill="#
|
|
154
|
-
<text x="
|
|
155
|
-
<text x="
|
|
156
|
-
<text x="
|
|
157
|
-
<text x="624.6" y="484" fill="#d0d0d0" xml:space="preserve">
|
|
158
|
-
<text x="726.0" y="484" fill="#87d787" xml:space="preserve">100%</text>
|
|
159
|
-
<text x="772.8" y="484" fill="#d0d0d0" xml:space="preserve">Router</text>
|
|
151
|
+
<text x="421.8" y="484" fill="#d0d0d0" xml:space="preserve">ctx </text>
|
|
152
|
+
<text x="453.0" y="484" fill="#87d787" xml:space="preserve">40%</text>
|
|
153
|
+
<text x="476.4" y="484" fill="#d0d0d0" xml:space="preserve"> · cache hit </text>
|
|
154
|
+
<text x="577.8" y="484" fill="#87d787" xml:space="preserve">100%</text>
|
|
155
|
+
<text x="624.6" y="484" fill="#d0d0d0" xml:space="preserve">Router</text>
|
|
160
156
|
</svg>
|