@alexeiled/claude-router 1.16.0 → 1.17.1
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 +32 -0
- package/README.md +33 -5
- package/docs/architecture.md +8 -4
- package/docs/configuration.md +68 -6
- package/docs/evaluation.md +34 -0
- package/docs/providers.md +222 -0
- package/docs/user-guide.md +20 -6
- package/hooks/native-router.mjs +69 -32
- package/lib/activity-stats.mjs +5 -3
- package/lib/activity.mjs +8 -3
- package/lib/config-file.mjs +5 -5
- package/lib/config.mjs +61 -11
- package/lib/cost.mjs +26 -4
- package/lib/decisions.mjs +4 -1
- package/lib/display.mjs +17 -6
- package/lib/facts.mjs +10 -0
- package/lib/panel.mjs +24 -9
- package/lib/providers.mjs +116 -0
- package/lib/route.mjs +48 -10
- package/lib/savings.mjs +43 -12
- package/lib/subagents.mjs +4 -3
- package/package.json +3 -2
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "router",
|
|
3
3
|
"displayName": "Router",
|
|
4
|
-
"version": "1.
|
|
5
|
-
"description": "
|
|
4
|
+
"version": "1.17.1",
|
|
5
|
+
"description": "Native model and effort routing within your provider. Anthropic, DeepSeek and z.ai 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,37 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.17.1 (2026-10-28)
|
|
4
|
+
|
|
5
|
+
### Fixed
|
|
6
|
+
|
|
7
|
+
- When the conversation fills more than 80% of every route's context window, the band and panel say `! context full` and the router keeps Claude's model. Before, they said `! model unavailable`, which read as an outage or an `availableModels` block. `model unavailable` now means only that: a model the allowlist blocks, one that overflowed its window, or one that cannot take images.
|
|
8
|
+
|
|
9
|
+
## 1.17.0 (2026-10-28)
|
|
10
|
+
|
|
11
|
+
Route models and effort within your configured provider. Anthropic remains the default. DeepSeek and z.ai gain built-in profiles, and other Anthropic-compatible providers can use custom profiles without another proxy.
|
|
12
|
+
|
|
13
|
+
### Added
|
|
14
|
+
|
|
15
|
+
- `CLAUDE_ROUTER_PROVIDER` selects `<provider>-router.json` in the active Claude Code profile. Selection stays fixed for the session, including pane Save/Undo. Missing or invalid selected files warn and preserve Claude Code's model and effort instead of falling back to `router.json`.
|
|
16
|
+
- DeepSeek Flash defaults route `low`, `high`, and `max` effort on one model. z.ai defaults combine GLM-5.3-Flash and GLM-5.3, with activity-specific routes.
|
|
17
|
+
- Custom profiles support OpenRouter, Ollama, other local servers and compatible hosted endpoints. Supply the model catalog and all four routes.
|
|
18
|
+
- [Provider documentation](docs/providers.md) covers names, defaults, custom files and the existing `--settings` flag alternative. There is no dedicated `--provider` flag.
|
|
19
|
+
|
|
20
|
+
### Changed
|
|
21
|
+
|
|
22
|
+
- Cache accounting supports explicit, automatic and disabled policies. Automatic caches use hit/miss input rates without invented TTLs or write premiums. Unknown counterfactual comparisons are reported separately from known observed costs.
|
|
23
|
+
- Model metadata can declare strength and image support. Provider allowlists use exact model identities, and the `[1m]` context hint is normalized without merging distinct versions.
|
|
24
|
+
|
|
25
|
+
### Upgrade
|
|
26
|
+
|
|
27
|
+
- Existing Anthropic users need no configuration change.
|
|
28
|
+
- Before selecting `deepseek` or `zai`, create its named router file. Use `{}` for built-in defaults. Other provider names require a complete profile.
|
|
29
|
+
- Set the selector before launching Claude Code. Project/local settings cannot redirect it.
|
|
30
|
+
|
|
31
|
+
### Limits
|
|
32
|
+
|
|
33
|
+
Routing stays within one configured endpoint. Subagents receive a model, not routed effort. Defaults are starting policies, not measured quality or savings guarantees. Positive z.ai cache hits remain unverified.
|
|
34
|
+
|
|
3
35
|
## 1.16.0 (2026-10-28)
|
|
4
36
|
|
|
5
37
|
Routing is now explainable after the fact, task notifications route as progress on the task they report on, and `cost` mode moves a hard task off Haiku. See [Routing decisions](docs/user-guide.md#routing-decisions) and [Changes during a task](docs/user-guide.md#changes-during-a-task).
|
package/README.md
CHANGED
|
@@ -5,11 +5,34 @@
|
|
|
5
5
|
|
|
6
6
|
**A Claude Code Mod that chooses a model and effort for each main-conversation turn, advised by a prompt classifier: Jev; Cloudflare's Clef, Clef Flash or Clef Omni; OpenAI; or a local Ollama model.**
|
|
7
7
|
|
|
8
|
-
The Mod changes only the model and effort in Claude Code's turn hook. Claude Code sends the request, streams the reply, runs tools, and reports usage. The router does not proxy
|
|
8
|
+
The Mod changes only the model and effort in Claude Code's turn hook. Claude Code sends the request, streams the reply, runs tools, and reports usage. The router does not proxy model traffic or start a local server; an Ollama classifier calls an Ollama server that you run. Subagents get one model each when they start, chosen the same way: every agent whose definition names no model, says `model: inherit`, or sets `modelRouting: auto`. Their steps are never re-routed. See [Subagent routing](docs/configuration.md#subagent-routing).
|
|
9
|
+
|
|
10
|
+
## Providers
|
|
11
|
+
|
|
12
|
+
Use the provider that already works with Claude Code. Select its router profile, not a new endpoint:
|
|
13
|
+
|
|
14
|
+
```sh
|
|
15
|
+
CLAUDE_ROUTER_PROVIDER=deepseek claude --model 'deepseek-flash[1m]'
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
Create `~/.claude/deepseek-router.json` containing `{}` to use DeepSeek defaults.
|
|
19
|
+
With `CLAUDE_CONFIG_DIR`, put the file in that directory instead.
|
|
20
|
+
|
|
21
|
+
| Built-in profile | Router file | Default models |
|
|
22
|
+
| --- | --- | --- |
|
|
23
|
+
| Anthropic, the default | `router.json` | Haiku 5.5, Sonnet 5.5, Opus 5.5 |
|
|
24
|
+
| `deepseek` | `deepseek-router.json` | DeepSeek Flash, routed by effort |
|
|
25
|
+
| `zai` | `zai-router.json` | GLM-5.3-Flash and GLM-5.3 |
|
|
26
|
+
|
|
27
|
+
OpenRouter, Ollama, other local servers and other compatible hosted providers use custom `<provider>-router.json` files.
|
|
28
|
+
They have no built-in model defaults. A selected file must exist and validate, or the router leaves Claude Code's model unchanged.
|
|
29
|
+
|
|
30
|
+
See [Providers](docs/providers.md) for **default routes and activities**, **custom profiles**, and the **`--settings` flag alternative**.
|
|
31
|
+
Execution provider selection is separate from classifier selection.
|
|
9
32
|
|
|
10
33
|
## Supported classifiers
|
|
11
34
|
|
|
12
|
-
The active classifier is asked at the start of each logical turn, for the tier and for the turn's activity, and again in the background every 4 requests while the turn runs (`policy.reviewEveryRequests`). Pick one on the pane's **Classifier** tab or in
|
|
35
|
+
The active classifier is asked at the start of each logical turn, for the tier and for the turn's activity, and again in the background every 4 requests while the turn runs (`policy.reviewEveryRequests`). Pick one on the pane's **Classifier** tab or in the selected router file; only the active one receives prompt text. With subagent routing `on` (the default), it is also asked once per routed subagent, with the task's description and prompt; set `"subagentRouting": "off"` to keep that text local.
|
|
13
36
|
|
|
14
37
|
| Classifier | Service | Credential | Prompt text goes to | How it is asked for the activity |
|
|
15
38
|
| ---------- | ------------------------------------------ | ----------------------------------- | ------------------------- | --------------------------------------------------------------------- |
|
|
@@ -36,7 +59,7 @@ sequenceDiagram
|
|
|
36
59
|
participant Code as Claude Code
|
|
37
60
|
participant Mod as Router Mod
|
|
38
61
|
participant Cls as Classifier
|
|
39
|
-
participant API as
|
|
62
|
+
participant API as Model provider
|
|
40
63
|
Dev->>Code: Prompt
|
|
41
64
|
opt Subagent spawn
|
|
42
65
|
Code->>Mod: agent.spawn
|
|
@@ -57,6 +80,8 @@ sequenceDiagram
|
|
|
57
80
|
|
|
58
81
|
The active classifier labels each new logical turn, and the router checks the route again while the task runs: a turn labelled `ops` that edits code moves up to the `code` route at once, and a background classifier review every 4 requests can move the tier or the activity either way. A cheaper route on the same task waits for a dwell and a checkpoint its work can show: a passed test, build or lint run, or for commands, docs and read-only work the success the router can see. A task notification is routed as progress on your last request. `/router decisions` lists why each turn ran where it did. See [Changes during a task](docs/user-guide.md#changes-during-a-task). A local policy applies vote, context, failure, and cache-cost rules before the Mod changes the next step. Claude Code owns request construction, model credentials, tools, streaming, and the API cost ledger.
|
|
59
82
|
|
|
83
|
+
With the Anthropic profile, the base routes are:
|
|
84
|
+
|
|
60
85
|
| Tier | Default model | Effort |
|
|
61
86
|
| -------- | ------------- | -------- |
|
|
62
87
|
| `micro` | Haiku 5.5 | `medium` |
|
|
@@ -68,6 +93,8 @@ These are routing defaults. They do not claim equal model quality. [Configuratio
|
|
|
68
93
|
|
|
69
94
|
Activity routing adds a second label: what the turn produces (`code`, `debug`, `explore`, `plan`, `review`, `ops`, or `docs`). A route is then picked by tier and activity. It is on by default since 1.7. A `·` cell uses the tier's own route, the base route:
|
|
70
95
|
|
|
96
|
+
The Anthropic profile uses these activity defaults. Other profiles have [their own defaults](docs/providers.md#activity-overrides).
|
|
97
|
+
|
|
71
98
|
| Activity | `micro` | `low` | `medium` | `high` |
|
|
72
99
|
| --------------------------------- | -------------- | ----------------- | ---------------- | ------------ |
|
|
73
100
|
| Base route | Haiku · medium | Haiku · high | Opus · medium | Opus · xhigh |
|
|
@@ -88,7 +115,7 @@ claude plugin marketplace add alexei-led/claude-router
|
|
|
88
115
|
claude plugin install router@alexei-led-claude-router
|
|
89
116
|
```
|
|
90
117
|
|
|
91
|
-
|
|
118
|
+
For the default Anthropic profile, start on the full baseline model, for example `claude --model claude-haiku-5-5`. For other providers, [select a provider profile](docs/providers.md#select-a-provider). Run `/plugin configure router` and save the key. For any other classifier, save its credentials, or run `ollama serve` with a pulled model, then pick the classifier on the pane's Classifier tab. A new session on a model that a tier routes to, or with activity routing `on` a model an activity override uses (Sonnet 5.5 on the defaults), starts with routing on; on any other model it starts with routing off and says why, and `/router auto` turns routing on.
|
|
92
119
|
|
|
93
120
|
Claude Code updates the plugin at startup when auto-update is on for this marketplace. Otherwise run `claude plugin marketplace update alexei-led-claude-router`, then `claude plugin update router@alexei-led-claude-router`.
|
|
94
121
|
|
|
@@ -116,7 +143,8 @@ npm run check && npm run typecheck && npm test && npm run validate && npm run te
|
|
|
116
143
|
## Documentation
|
|
117
144
|
|
|
118
145
|
- [User guide](docs/user-guide.md): install, use the controls, read the panel, and troubleshoot.
|
|
119
|
-
- [
|
|
146
|
+
- [Providers](docs/providers.md): provider names, router files, built-in defaults, and custom profiles.
|
|
147
|
+
- [Configuration](docs/configuration.md): router-file settings, classifier keys, cache policies, and migrations.
|
|
120
148
|
- [Architecture](docs/architecture.md): Mod event flow, state, safeguards, and runtime boundaries.
|
|
121
149
|
- [Activity routing](docs/activity-routing.md): the default matrix by activity, why each cell, and how to change or turn it off.
|
|
122
150
|
- [Routing modes](docs/routing-modes.md): `cost`, `balanced` and `quality`, where the mode comes from, and every decision per mode.
|
package/docs/architecture.md
CHANGED
|
@@ -11,7 +11,7 @@ sequenceDiagram
|
|
|
11
11
|
participant Code as Claude Code
|
|
12
12
|
participant Mod as Router Mod
|
|
13
13
|
participant Cls as Classifier
|
|
14
|
-
participant API as
|
|
14
|
+
participant API as Model provider
|
|
15
15
|
Dev->>Code: Prompt
|
|
16
16
|
Code->>Mod: turn.start and turn.step
|
|
17
17
|
alt Main conversation, routing on
|
|
@@ -91,7 +91,7 @@ The router decides on a _cell_: a tier and an activity. The route is `{ ...route
|
|
|
91
91
|
1. **Pin.** A pinned tier wins, with no activity: the pin's tier route.
|
|
92
92
|
2. **Activity.** Only in `on`; `off` uses none, and ignores the activity a turn in `on` ran with before the mode changed. With no advice, or advice without an activity answer, the incumbent's activity stays. On the same task (`sameTaskOf`; Ollama gives no continuation answer, so only reviews count for it) a label whose route at the incumbent tier is stronger applies at once, and a weaker one only with at least `downgradeMass` probability once `facts.downAllowed` holds; an unclear label keeps the running activity. Otherwise the activity with probability at least `activityMass` applies; below that, or for `uncertain`, there is none and the tier's base route is used.
|
|
93
93
|
3. **Tier.** The tier policy runs as before, with every candidate tier priced at its route for the activity and the incumbent at the route it runs. Repeated tool errors move to the lowest tier above whose route is stronger than the running one, or sends a request that cannot be ordered against it. With no activity that is one tier up, as in 1.5. If no tier above helps, nothing escalates and the failure signature is kept.
|
|
94
|
-
4. **Lateral move.** If the tier stays and the route would change, `lateralMove` decides. Routes order by
|
|
94
|
+
4. **Lateral move.** If the tier stays and the route would change, `lateralMove` decides. Routes order by explicit model strength when both models declare it, otherwise by output price, then effort; a session effort counts as the effort Claude Code sends. Two routes that send the same request do not switch. A pair that cannot be ordered (an unpriced model, a numeric effort, two models at one price) counts as a move up, so the base route is always reachable. A stronger route needs the activity's probability to clear the upgrade bar for its switching tax (a base route with no activity counts as probability 1). A cheaper route needs its downgrade tax to be paid back within `downgradeHorizonTurns`, except before the first measured reply of a history, when there is no cache to protect. The cash gate applies to both. The result is `activity-up`, `activity-down`, `activity-pending` (stay on the running route and its activity), `cash-gate`, or `hold`. While an escalation hold lasts, only a stronger route may be taken. One vote is enough: an activity is a fact about the turn, not a noisy estimate. If the tier changes, the tier gates have already priced the new route, and no lateral rule applies.
|
|
95
95
|
5. **Fit.** Context fit and model availability resolve through `route(tier, activity)`. A fallback tries the last cell, the native model's cell, then each tier with the activity. The last and the native cell count only when they carry no activity or the turn's; otherwise, or when nothing fits, the native model runs at the session effort.
|
|
96
96
|
|
|
97
97
|
**Observed move.** On each later step of the turn, `observedMove` reads the turn's tool calls since its prompt, or since the transcript snapshot of the last review applied inside the turn (`loop.observedFrom`), since the review already judged the earlier ones, (`observedActivity`: `code` after an edit to a non-doc file, `docs` after edits to doc files only, else `ops`, `read` or `talk`). When that activity's route at the decision's tier is stronger than the running one, the remaining steps take it, with reason `activity-up` and `lastActivity` set, so the next turn starts there. The tier is fitted to the context first, so the gates price the route that will run. It goes through `lateralMove` with probability 1: the tools are the evidence, so the switching tax never holds it back (the upgrade bar tops out near 0.9), and only the cash gate can. The turn's reply label (`turnActivities.label`) follows the move; the classifier's answer stays as recorded. It never moves down, and skips pinned turns and `off`. `canMoveUp` skips the transcript read when no activity's route at the tier is stronger, so a step on the strongest route costs nothing. A move to a smaller window waits for a measured context, as in `routeTurn`. Context fit and model availability then apply as for any continuation.
|
|
@@ -127,7 +127,7 @@ When a turn completes, the Mod labels it from the tool calls the assistant made
|
|
|
127
127
|
Two stores hold counts:
|
|
128
128
|
|
|
129
129
|
- **Session**: `activityStats` in the view, reset when the session ends. It has turns, requests, tokens, the list price of priced replies with their count, and routed replies by `model@effort` per activity, switches by tier and by activity, lateral moves taken and refused, and tool agreement. The label counted per activity is the applied activity in `on`. Tool agreement compares the answer that cleared `activityMass`, so it measures the classifier in both modes. The view also keeps `strip`, every reply since Claude Code started the session by tier in at most 48 cells that merge in pairs, with when its first reply arrived, and `lastSwitch`, the last route change with its tiers, routes and activity.
|
|
130
|
-
- **Across sessions**: two `$.store` records per session. Each session's `activity:stats:v1:<session id>` holds a confusion matrix of the classifier's raw answer (including `uncertain` and `none`) against the observed bucket, run lengths per activity in five buckets, lateral switches taken and refused (from the decision's `lateral` field, so a hold or the cash gate counts), and `since`, its first count. A value with an unknown key or shape reads as empty; the `shadow` key that versions before 1.10.1 wrote is dropped on read and the rest is kept. Before 1.10.3 every session shared one `activity:stats:v1` key, read-modified-written each turn, so two sessions finishing turns together could lose a count and a stale write could undo a reset; that key now counts as one more record in the sum until **Delete history** deletes it, and 1.10.2 and earlier read only it. Each session's `activity:metrics:v1:<session id>` holds a classifier latency histogram per classifier id (22 buckets, at most 8 ids), the cheaper activity moves taken in `on` with the escalations that followed one, the routed replies
|
|
130
|
+
- **Across sessions**: two `$.store` records per session. Each session's `activity:stats:v1:<session id>` holds a confusion matrix of the classifier's raw answer (including `uncertain` and `none`) against the observed bucket, run lengths per activity in five buckets, lateral switches taken and refused (from the decision's `lateral` field, so a hold or the cash gate counts), and `since`, its first count. A value with an unknown key or shape reads as empty; the `shadow` key that versions before 1.10.1 wrote is dropped on read and the rest is kept. Before 1.10.3 every session shared one `activity:stats:v1` key, read-modified-written each turn, so two sessions finishing turns together could lose a count and a stale write could undo a reset; that key now counts as one more record in the sum until **Delete history** deletes it, and 1.10.2 and earlier read only it. Each session's `activity:metrics:v1:<session id>` holds a classifier latency histogram per classifier id (22 buckets, at most 8 ids), the cheaper activity moves taken in `on` with the escalations that followed one, the routed replies excluded from usage comparisons by cause (`unpriced`: `usage`, `model`, `ttl`, `error`, `comparison`, from `unpricedCause` in `lib/savings.mjs`; 1.16), and `since`, its first reading; each part reads as empty on its own when its shape is wrong, as after a change of buckets. Both follow the usage records below: one writer per key, so sessions that finish turns at the same moment do not overwrite each other; this session's record held in memory and written after each turn that adds a count; the readout the sum of all records, latency kept to the first 8 classifier ids; and the same reset marker. Each record is bounded, and the records grow by one per session that recorded a count until **Delete history**. The view keeps the last sums read or written as `activityStore` and `activityMetrics`: read at session start and when the pane opens, replaced after each turn's write and after a reset. The open run is written when the session ends. **Delete history** clears the session counts, every stats and metrics record, and the usage records below.
|
|
131
131
|
|
|
132
132
|
Nothing is recorded with `activityRouting: off`. Stats run inside a guard: a failed transcript read or store access loses that turn's counts and never fails the turn. Readings already in the session's metrics record stay in memory after a failed write and go out with the next turn that adds a reading. A turn from a session that has since changed is dropped.
|
|
133
133
|
|
|
@@ -157,7 +157,11 @@ In a 20-process loopback test, timeout fallback had 1,504 ms p95 and 1,505 ms wo
|
|
|
157
157
|
|
|
158
158
|
## Cache and cost
|
|
159
159
|
|
|
160
|
-
|
|
160
|
+
Execution profile selection is fixed at session start by `CLAUDE_ROUTER_PROVIDER`: unset/`anthropic` reads `router.json`, another validated ID reads `<provider>-router.json` in the same profile directory. Missing or invalid selected files pass requests through, never fall back to the default file. Save/Undo keep that path. Provider presets replace execution routes, activities, models and subagent defaults, not classifier credentials. See [Providers](providers.md).
|
|
161
|
+
|
|
162
|
+
The explicit-cache rules below describe Anthropic. Automatic prefix-cache providers instead use observed hit/miss input rates, no write premium and no guaranteed TTL. Their future price bounds allow a full miss; counterfactual cache comparisons are omitted unless the observed route is identical. Same-model effort downgrades skip input-only payback, which cannot value generated thinking-token changes, but retain the vote, dwell and cold-input guards. Their cache observations remain effort-specific until sharing is established. `disabled` cache mode uses the uncached input rate throughout.
|
|
163
|
+
|
|
164
|
+
Cache identity uses the response model ID with the `[1m]` context hint removed, plus the effective effort on models that keep one cache per effort. Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable 5.1 keep one cache across efforts with an API key or a Claude subscription (code.claude.com/docs/en/prompt-caching, "Changing effort level"), so an effort-only move costs no cache write there. The hook gives every effort its own cache when the session runs on Amazon Bedrock, Google Cloud, Microsoft Foundry, a custom `ANTHROPIC_BASE_URL`, or with `CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS` (`effortSplitsCache`). A HIPAA configuration is not visible to a Mod; there the router prices effort moves as free. The Haiku 4.5 dated snapshot has an explicit mapping; Haiku 5.5 has no dated ID. An unrecognized substituted model gets no cache credit for the requested route.
|
|
161
165
|
|
|
162
166
|
The cached prefix is observed `cache_read + cache_creation`. Output tokens count only toward the next context size. Freshness uses the configured five-minute lifetime with its safety margin. Claude's usage counters do not prove one-hour cache lifetime.
|
|
163
167
|
|
package/docs/configuration.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Configuration
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Select a [provider profile](providers.md), then configure the key of the classifier you use. This page describes the settings inside the selected router file.
|
|
4
4
|
|
|
5
5
|
## Key and profile settings
|
|
6
6
|
|
|
@@ -10,8 +10,8 @@ The router works with its built-in defaults. Configure the key of the active cla
|
|
|
10
10
|
| Cloudflare API token | Sensitive plugin option `cloudflare_api_token` | The same dialog. Used by Clef, Clef Flash and Clef Omni. |
|
|
11
11
|
| Cloudflare account ID | Plugin option `cloudflare_account_id` | The same dialog, or the config menu row. Not a secret. |
|
|
12
12
|
| OpenAI API key | Sensitive plugin option `openai_api_key` | The same dialog. Used only by the OpenAI classifier. Ollama needs no key. |
|
|
13
|
-
| Router settings and classifier |
|
|
14
|
-
|
|
|
13
|
+
| Router settings and classifier | The selected router file in the active Claude Code profile | Edit the file directly, or use the pane's Routes, Policy and Classifier tabs. |
|
|
14
|
+
| Execution provider credentials and API cost | Claude Code | The Mod leaves these to Claude Code. |
|
|
15
15
|
|
|
16
16
|
The active profile directory is `CLAUDE_CONFIG_DIR` when set. Otherwise it is `~/.claude`. The Mod does not need an Anthropic proxy URL, model alias, hint header, daemon, or custom status line.
|
|
17
17
|
|
|
@@ -26,7 +26,69 @@ The Mod reads each value from its plugin option first. When the option is empty,
|
|
|
26
26
|
|
|
27
27
|
Export the variables before you start `claude`. Without the key or the account ID of the active classifier, the Mod keeps Claude's current model and reports which value is missing.
|
|
28
28
|
|
|
29
|
-
Project and local settings cannot set `HOME` or `
|
|
29
|
+
Project and local settings cannot set `HOME`, `CLAUDE_CONFIG_DIR`, or `CLAUDE_ROUTER_PROVIDER` for this Mod. Those overrides make the router unavailable for the session, so a project cannot redirect the router to another profile's key or configuration.
|
|
30
|
+
|
|
31
|
+
## Provider profiles
|
|
32
|
+
|
|
33
|
+
Set `CLAUDE_ROUTER_PROVIDER` to select `<provider>-router.json` in the active Claude Code profile.
|
|
34
|
+
Unset, empty, or `anthropic` selects `router.json`.
|
|
35
|
+
See [Providers](providers.md) for selection examples, built-in defaults and complete custom profiles.
|
|
36
|
+
|
|
37
|
+
The same schema applies to every router file. This reference uses `router.json` as shorthand for the selected file.
|
|
38
|
+
A non-Anthropic file must exist and validate. It never falls back to `router.json` or inherits settings from it.
|
|
39
|
+
|
|
40
|
+
### Provider prices
|
|
41
|
+
|
|
42
|
+
DeepSeek and z.ai default windows are 1M tokens.
|
|
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
|
+
These rates were checked on 2026-10-28.
|
|
45
|
+
|
|
46
|
+
| Model | Input / output / cached input, USD per million tokens |
|
|
47
|
+
| --- | --- |
|
|
48
|
+
| DeepSeek Flash | 0.30 / 1.20 / 0.006 |
|
|
49
|
+
| GLM-5.3-Flash | 0.15 / 0.50 / 0.03 |
|
|
50
|
+
| GLM-5.3 | 1.40 / 4.40 / 0.26 |
|
|
51
|
+
|
|
52
|
+
These are fixed estimate inputs, not an invoice. DeepSeek off-peak rates differ, and z.ai plan quota uses its own multipliers.
|
|
53
|
+
Both presets use `billing: "credits"`.
|
|
54
|
+
For an included-plan model, set `billing: "plan"` to disable the cold-input cash cap.
|
|
55
|
+
A provider name or URL does not establish its billing product.
|
|
56
|
+
|
|
57
|
+
### Provider cache behavior
|
|
58
|
+
|
|
59
|
+
`cache.mode` controls the router's cost estimates, not the provider's server cache.
|
|
60
|
+
|
|
61
|
+
| Mode | Use | Estimate |
|
|
62
|
+
| --- | --- | --- |
|
|
63
|
+
| `explicit` | Anthropic default | Configured write multipliers and TTLs |
|
|
64
|
+
| `automatic` | DeepSeek, z.ai and custom-profile default | Reported hit/miss input rates, no separate write premium |
|
|
65
|
+
| `disabled` | No cache discount to model | All input at the uncached rate, never marked warm |
|
|
66
|
+
|
|
67
|
+
Automatic-cache bounds allow a future hit or a full miss, including after an observed miss.
|
|
68
|
+
The router does not assume a five-minute or one-hour lifetime. Payback is unknown.
|
|
69
|
+
Same-model effort changes retain votes, dwell and the cold-input cap.
|
|
70
|
+
They skip fixed-token payback because it cannot value changes in generated thinking tokens.
|
|
71
|
+
|
|
72
|
+
`cache.effortScope` accepts these values:
|
|
73
|
+
|
|
74
|
+
| Value | Meaning |
|
|
75
|
+
| --- | --- |
|
|
76
|
+
| `auto` | Existing Claude cache detection |
|
|
77
|
+
| `shared` | One cache identity across efforts |
|
|
78
|
+
| `separate` | One cache identity per effort |
|
|
79
|
+
| `unknown` | Keep observations separate without claiming that the provider separates caches |
|
|
80
|
+
|
|
81
|
+
Automatic-cache presets use `unknown`. Set `shared` only when the provider contract establishes sharing.
|
|
82
|
+
An unknown cache state is not proof of a miss.
|
|
83
|
+
|
|
84
|
+
[DeepSeek caching](https://api-docs.deepseek.com/guides/kv_cache) is automatic and best-effort. Its Anthropic endpoint ignores explicit cache controls.
|
|
85
|
+
[z.ai caching](https://docs.z.ai/guides/capabilities/cache.md) has no verified model-specific TTL.
|
|
86
|
+
Claude Code's `DISABLE_PROMPT_CACHING` does not establish whether an automatic server cache is disabled.
|
|
87
|
+
|
|
88
|
+
Valid observed usage can still be priced for activity statistics.
|
|
89
|
+
For automatic caches, routing-versus-your-model comparisons require an identical observed route.
|
|
90
|
+
Otherwise the UI reports comparison unavailable. It does not label a known observed cost unpriced or invent another route's hit rate.
|
|
91
|
+
Missing counters remain unknown. See [provider acceptance checks](evaluation.md#provider-profiles).
|
|
30
92
|
|
|
31
93
|
## Built-in defaults
|
|
32
94
|
|
|
@@ -251,8 +313,8 @@ The Mod validates the whole file. Unknown keys and invalid values make routing u
|
|
|
251
313
|
| `mode` | `cost`, `balanced`, `quality` ([Routing modes](routing-modes.md)) | `balanced` |
|
|
252
314
|
| `modes.<cost\|quality>.policy` | any `policy` field, used while that mode is active | [Routing modes](routing-modes.md#policy-per-mode); not tuned |
|
|
253
315
|
| `activities.<activity>.<tier>` | optional `model` and `effort`, as in `routes` | The overrides in [Activity routing](#activity-routing) |
|
|
254
|
-
| `models.<alias>` | `id`, `input`, optional `output`, `cacheRead`, optional `longContext` (`above`, `multiplier`, or `null`), `contextWindow`, `billing`, `efforts` | Three defaults above |
|
|
255
|
-
| `cache` | `writeMultiplier`, `ttlMs`, `warmMarginMs` | `5m: 1.25`, `1h: 2`; `300000` / `3600000` ms; `30000` ms |
|
|
316
|
+
| `models.<alias>` | `id`, `input`, optional `output`, `cacheRead`, optional `longContext` (`above`, `multiplier`, or `null`), `contextWindow`, `billing`, `efforts`, optional `strength`, `imageInput` | Three defaults above |
|
|
317
|
+
| `cache` | `mode`, `effortScope`, `writeMultiplier`, `ttlMs`, `warmMarginMs` | `5m: 1.25`, `1h: 2`; `300000` / `3600000` ms; `30000` ms |
|
|
256
318
|
| `policy` | Fields below | Values below |
|
|
257
319
|
| `classifier` | An id in `classifiers` | `jev` |
|
|
258
320
|
| `classifiers.<id>` | `label`, `api`, `endpoint`, `model`, `keyOption`, `timeoutMs` | [Classifiers](#classifiers) above |
|
package/docs/evaluation.md
CHANGED
|
@@ -4,6 +4,40 @@ The native Mod has no measured savings result. The pane reports Claude's own usa
|
|
|
4
4
|
|
|
5
5
|
This page separates an older gateway experiment from a shadow replay of native policy. Neither result measures answer quality or proves lower real spend. [Activity routing](#activity-routing) adds two checks of the activity label, with no savings result either.
|
|
6
6
|
|
|
7
|
+
## Provider profiles
|
|
8
|
+
|
|
9
|
+
[Provider defaults](providers.md#built-in-defaults) are starting policies, not measured per-activity quality or savings results.
|
|
10
|
+
|
|
11
|
+
The model and effort choices use official [DeepSeek controls](https://api-docs.deepseek.com/guides/thinking_mode), [z.ai controls](https://docs.z.ai/guides/capabilities/thinking.md), and [Coding Plan mappings](https://docs.z.ai/devpack/latest-model.md).
|
|
12
|
+
The model-cards knowledgebase supplied model-specific controls and prompting constraints.
|
|
13
|
+
|
|
14
|
+
Artificial Analysis profiles informed activity choices:
|
|
15
|
+
|
|
16
|
+
- [GLM-5.3](https://artificialanalysis.ai/models/glm-5-3)
|
|
17
|
+
- [GLM-5.3-Flash](https://artificialanalysis.ai/models/glm-5-3-flash)
|
|
18
|
+
- [DeepSeek-V4.1-Flash](https://artificialanalysis.ai/models/deepseek-v4-1-flash)
|
|
19
|
+
|
|
20
|
+
Terminal engineering and SRE results differ. Neither GLM model leads every activity.
|
|
21
|
+
Measured max-effort results do not establish low/high performance or an optimal routing matrix.
|
|
22
|
+
The original DeepSeek benchmark profile does not establish the quality of its newer hosted 1017 snapshot.
|
|
23
|
+
|
|
24
|
+
### Compatibility checks
|
|
25
|
+
|
|
26
|
+
On 2026-10-28, six synthetic live requests per provider returned HTTP 200.
|
|
27
|
+
The requests covered `low`, `high`, and `max` on DeepSeek Flash and both GLM models.
|
|
28
|
+
DeepSeek reported 2,688 cache-read tokens on repeated requests. z.ai reported zero hits in that sample.
|
|
29
|
+
|
|
30
|
+
These checks establish accepted request and usage-counter shapes.
|
|
31
|
+
They do not establish a guaranteed cache hit rate, cross-effort cache sharing, answer quality, or savings.
|
|
32
|
+
Claude Code 2.1.312 supplied zero when the z.ai-style response omitted cache-creation tokens.
|
|
33
|
+
|
|
34
|
+
`npm run test:providers` checks the production Mod against a loopback API with synthetic credentials.
|
|
35
|
+
It covers provider selection through a `--settings` environment layer, model/effort switches, tool continuations, and missing/invalid profiles.
|
|
36
|
+
It also covers omitted cache-creation counters. The command makes no paid provider calls.
|
|
37
|
+
|
|
38
|
+
OpenRouter, Ollama and other [custom profiles](providers.md#add-another-provider) have no provider-specific acceptance result here.
|
|
39
|
+
A valid configuration does not establish backend compatibility or model quality.
|
|
40
|
+
|
|
7
41
|
## Historical gateway experiment
|
|
8
42
|
|
|
9
43
|
These figures are retained from the earlier gateway implementation. They do not evaluate the native Mod or its current routes. The snapshot covers 26 Claude Code sessions and 1,611 requests from 2026-09-23 09:05 UTC through 2026-09-24 06:00 UTC. Jev advised on 111 prompts.
|
|
@@ -0,0 +1,222 @@
|
|
|
1
|
+
# Providers
|
|
2
|
+
|
|
3
|
+
Claude Router routes models and effort within the provider that Claude Code already uses.
|
|
4
|
+
Set a provider name and give the router a matching JSON file. No provider-specific plugin or proxy is needed.
|
|
5
|
+
|
|
6
|
+
**Built-in profiles:** Anthropic, DeepSeek and z.ai.
|
|
7
|
+
**Custom profiles:** OpenRouter, Ollama, other local servers, and other hosted providers with a Claude Code-compatible Anthropic endpoint.
|
|
8
|
+
Custom profiles need their own model settings. They do not inherit Claude models.
|
|
9
|
+
|
|
10
|
+
This guide assumes Claude Code already works with your provider. Endpoint and credential setup are outside its scope.
|
|
11
|
+
|
|
12
|
+
## Select a provider
|
|
13
|
+
|
|
14
|
+
For DeepSeek, create `deepseek-router.json` in your Claude Code profile directory with this content:
|
|
15
|
+
|
|
16
|
+
```json
|
|
17
|
+
{}
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
Then start Claude Code:
|
|
21
|
+
|
|
22
|
+
```sh
|
|
23
|
+
CLAUDE_ROUTER_PROVIDER=deepseek claude --model 'deepseek-flash[1m]'
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
The empty file enables DeepSeek's built-in defaults. Change only the settings you want to override.
|
|
27
|
+
|
|
28
|
+
If you prefer a command-line flag, use Claude Code's existing `--settings` flag:
|
|
29
|
+
|
|
30
|
+
```sh
|
|
31
|
+
claude --settings '{"env":{"CLAUDE_ROUTER_PROVIDER":"deepseek"}}' --model 'deepseek-flash[1m]'
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
There is no separate `--provider` flag. A launcher can set `CLAUDE_ROUTER_PROVIDER` for each launch.
|
|
35
|
+
|
|
36
|
+
### Name-to-file mapping
|
|
37
|
+
|
|
38
|
+
The directory is `CLAUDE_CONFIG_DIR` when set, otherwise `~/.claude`.
|
|
39
|
+
|
|
40
|
+
| Provider name | Router file | Built-in model defaults |
|
|
41
|
+
| --- | --- | --- |
|
|
42
|
+
| Unset, empty, or `anthropic` | `router.json` | Haiku 5.5, Sonnet 5.5, Opus 5.5 |
|
|
43
|
+
| `deepseek` | `deepseek-router.json` | DeepSeek Flash |
|
|
44
|
+
| `zai` | `zai-router.json` | GLM-5.3-Flash, GLM-5.3 |
|
|
45
|
+
| `openrouter` | `openrouter-router.json` | None. Supply a complete profile. |
|
|
46
|
+
| `ollama` | `ollama-router.json` | None. Supply a complete profile. |
|
|
47
|
+
| Any other valid name | `<provider>-router.json` | None. Supply a complete profile. |
|
|
48
|
+
|
|
49
|
+
Names are local profile identifiers, not a provider registry or an endpoint lookup.
|
|
50
|
+
For example, `minimax`, `kimi`, `mimo`, or `local` can name a custom profile.
|
|
51
|
+
Names must start with a lowercase letter, contain only lowercase letters, digits and hyphens, and have at most 64 characters.
|
|
52
|
+
|
|
53
|
+
**Setting the name does not change Claude Code's endpoint, credentials or billing product.**
|
|
54
|
+
The router neither detects providers from URLs nor switches endpoints between turns.
|
|
55
|
+
|
|
56
|
+
### File rules
|
|
57
|
+
|
|
58
|
+
- A non-Anthropic profile file must exist. Only the Anthropic profile can run without a file.
|
|
59
|
+
- Missing or invalid files produce a warning and leave Claude Code's model and effort unchanged.
|
|
60
|
+
- The router never falls back from a selected provider file to `router.json`.
|
|
61
|
+
- Profiles are independent. Classifier, policy and route overrides in `router.json` do not carry over.
|
|
62
|
+
- Selection is fixed for the session. The pane shows the selected file and writes Save/Undo changes there.
|
|
63
|
+
- Project and local settings cannot redirect the profile with `CLAUDE_ROUTER_PROVIDER`, `CLAUDE_CONFIG_DIR`, or `HOME`.
|
|
64
|
+
|
|
65
|
+
Select a classifier separately. Using Ollama to run your coding model does not also select Ollama as the classifier.
|
|
66
|
+
For an all-local setup, [configure the Ollama classifier](user-guide.md#use-ollama) in your local provider profile.
|
|
67
|
+
|
|
68
|
+
## Built-in defaults
|
|
69
|
+
|
|
70
|
+
Anthropic is the default when no provider name is set.
|
|
71
|
+
DeepSeek and z.ai require their named files, even when you want only defaults.
|
|
72
|
+
A file containing `{}` is enough for either.
|
|
73
|
+
|
|
74
|
+
### Model IDs
|
|
75
|
+
|
|
76
|
+
| Profile | Alias | Model ID |
|
|
77
|
+
| --- | --- | --- |
|
|
78
|
+
| Anthropic | `haiku` | `claude-haiku-5-5` |
|
|
79
|
+
| Anthropic | `sonnet` | `claude-sonnet-5-5` |
|
|
80
|
+
| Anthropic | `opus` | `claude-opus-5-5` |
|
|
81
|
+
| DeepSeek | `flash` | `deepseek-flash[1m]` |
|
|
82
|
+
| z.ai | `flash` | `glm-5.3-flash[1m]` |
|
|
83
|
+
| z.ai | `glm` | `glm-5.3[1m]` |
|
|
84
|
+
|
|
85
|
+
`[1m]` is a Claude Code context hint, not a different served model.
|
|
86
|
+
Changing Claude Code's model-slot environment variables does not update this catalog.
|
|
87
|
+
If you use different models, update their IDs and metadata in the selected router file.
|
|
88
|
+
|
|
89
|
+
### Default routes
|
|
90
|
+
|
|
91
|
+
Each cell is `model alias · effort`. All profiles start at tier `low`.
|
|
92
|
+
|
|
93
|
+
| Profile | `micro` | `low` | `medium` | `high` |
|
|
94
|
+
| --- | --- | --- | --- | --- |
|
|
95
|
+
| Anthropic | haiku · medium | haiku · high | opus · medium | opus · xhigh |
|
|
96
|
+
| DeepSeek | flash · low | flash · high | flash · high | flash · max |
|
|
97
|
+
| z.ai | flash · low | flash · high | glm · high | glm · max |
|
|
98
|
+
|
|
99
|
+
A provider can use one model at several efforts. Two tiers can also share the same model and effort.
|
|
100
|
+
|
|
101
|
+
### Activity overrides
|
|
102
|
+
|
|
103
|
+
With activity routing on, these cells replace the base route. Other cells keep the base route.
|
|
104
|
+
|
|
105
|
+
| Profile | Activities | Tier | Route |
|
|
106
|
+
| --- | --- | --- | --- |
|
|
107
|
+
| Anthropic | `code`, `debug`, `plan`, `review` | `low` | sonnet · high |
|
|
108
|
+
| Anthropic | `ops` | `medium` | haiku · high |
|
|
109
|
+
| DeepSeek | `code`, `debug`, `plan`, `review` | `medium` | flash · max |
|
|
110
|
+
| z.ai | `code`, `debug`, `plan`, `review` | `medium` | glm · max |
|
|
111
|
+
| z.ai | `ops`, `explore`, `docs` | `medium` | flash · high |
|
|
112
|
+
| z.ai | `ops`, `explore`, `docs` | `high` | flash · max |
|
|
113
|
+
|
|
114
|
+
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 1M-token context window.
|
|
116
|
+
|
|
117
|
+
Subagent routing is on for built-in profiles:
|
|
118
|
+
|
|
119
|
+
| Profile | Light | Standard | Heavy |
|
|
120
|
+
| --- | --- | --- | --- |
|
|
121
|
+
| Anthropic | haiku | sonnet | opus |
|
|
122
|
+
| DeepSeek | flash | flash | flash |
|
|
123
|
+
| z.ai | flash | glm | glm |
|
|
124
|
+
|
|
125
|
+
Subagents receive a model at spawn, not a routed effort. Their own effort setting still applies.
|
|
126
|
+
|
|
127
|
+
These defaults are starting policies, not measured quality or savings guarantees.
|
|
128
|
+
See [the evidence and limits](evaluation.md#provider-profiles).
|
|
129
|
+
For prices and cache settings, see [the configuration reference](configuration.md#provider-profiles).
|
|
130
|
+
|
|
131
|
+
## Add another provider
|
|
132
|
+
|
|
133
|
+
No code change or provider registration is needed.
|
|
134
|
+
Choose a name, create its file, and set `CLAUDE_ROUTER_PROVIDER` to that name.
|
|
135
|
+
|
|
136
|
+
Unlike built-in profiles, a custom profile cannot use only `{}`.
|
|
137
|
+
Define all four routes and a complete model entry for each model they reference.
|
|
138
|
+
Custom profiles start with subagent routing off and automatic-cache accounting.
|
|
139
|
+
|
|
140
|
+
### Example: two local models
|
|
141
|
+
|
|
142
|
+
Save the following as `ollama-router.json` in your Claude Code profile directory.
|
|
143
|
+
Replace the two placeholder IDs with models installed on your server.
|
|
144
|
+
Set each context window to the limit configured for that model.
|
|
145
|
+
|
|
146
|
+
This example assumes local models with no per-token charge and no exposed effort control.
|
|
147
|
+
The zero prices and 32K windows are example settings, not defaults for every Ollama model.
|
|
148
|
+
|
|
149
|
+
```json
|
|
150
|
+
{
|
|
151
|
+
"models": {
|
|
152
|
+
"fast": {
|
|
153
|
+
"id": "your-fast-model",
|
|
154
|
+
"input": 0,
|
|
155
|
+
"output": 0,
|
|
156
|
+
"cacheRead": 0,
|
|
157
|
+
"contextWindow": 32768,
|
|
158
|
+
"billing": "plan",
|
|
159
|
+
"efforts": [],
|
|
160
|
+
"strength": 1,
|
|
161
|
+
"imageInput": false
|
|
162
|
+
},
|
|
163
|
+
"strong": {
|
|
164
|
+
"id": "your-strong-model",
|
|
165
|
+
"input": 0,
|
|
166
|
+
"output": 0,
|
|
167
|
+
"cacheRead": 0,
|
|
168
|
+
"contextWindow": 32768,
|
|
169
|
+
"billing": "plan",
|
|
170
|
+
"efforts": [],
|
|
171
|
+
"strength": 2,
|
|
172
|
+
"imageInput": false
|
|
173
|
+
}
|
|
174
|
+
},
|
|
175
|
+
"routes": {
|
|
176
|
+
"micro": { "model": "fast", "effort": null },
|
|
177
|
+
"low": { "model": "fast", "effort": null },
|
|
178
|
+
"medium": { "model": "strong", "effort": null },
|
|
179
|
+
"high": { "model": "strong", "effort": null }
|
|
180
|
+
},
|
|
181
|
+
"cache": { "mode": "disabled" }
|
|
182
|
+
}
|
|
183
|
+
```
|
|
184
|
+
|
|
185
|
+
Start with the fast model, after replacing its placeholder ID:
|
|
186
|
+
|
|
187
|
+
```sh
|
|
188
|
+
CLAUDE_ROUTER_PROVIDER=ollama claude --model your-fast-model
|
|
189
|
+
```
|
|
190
|
+
|
|
191
|
+
`cache.mode` controls the router's cost estimates. It does not disable a server's internal cache.
|
|
192
|
+
Here it avoids assuming a billed prompt cache for the local models.
|
|
193
|
+
|
|
194
|
+
The same profile format works for OpenRouter or another hosted provider.
|
|
195
|
+
Use that provider's model IDs, supported efforts, context limits and actual token prices instead of the local example values.
|
|
196
|
+
Use `billing: "credits"` for token-billed models.
|
|
197
|
+
Set the [cache policy](configuration.md#provider-cache-behavior) to match the provider.
|
|
198
|
+
|
|
199
|
+
### Model and effort rules
|
|
200
|
+
|
|
201
|
+
- Alias names such as `fast` and `strong` are yours to choose. Routes refer to aliases, not API IDs.
|
|
202
|
+
- `efforts` lists only the effort levels that Claude Code can send and the provider honors.
|
|
203
|
+
- With `efforts: []`, use `effort: null` in every route. This omits routed effort, not model thinking.
|
|
204
|
+
- With named efforts, use only levels listed for that model. API compatibility does not make effort names equivalent.
|
|
205
|
+
- `strength` orders models for routing. A higher price does not prove higher capability.
|
|
206
|
+
- Prices are USD per million tokens. Use zero only when there is no token charge.
|
|
207
|
+
- `imageInput` describes the model's actual input support, not the provider's general capabilities.
|
|
208
|
+
|
|
209
|
+
For the full schema, see [Configuration](configuration.md#optional-routerjson).
|
|
210
|
+
To enable custom subagent routes, also configure [subagent routing](configuration.md#subagent-routing).
|
|
211
|
+
|
|
212
|
+
## Check the selected profile
|
|
213
|
+
|
|
214
|
+
1. Open `/router` and check the provider name and file path.
|
|
215
|
+
2. Start on a model used by a configured route, or run `/router auto`.
|
|
216
|
+
3. Check that the band names the expected model and effort after a prompt.
|
|
217
|
+
|
|
218
|
+
If routing is unavailable, inspect the selected file first.
|
|
219
|
+
A typo in the provider name selects a different filename. It does not choose the default profile.
|
|
220
|
+
|
|
221
|
+
Changing a provider name requires a new session.
|
|
222
|
+
Pane edits stay within the selected profile and apply from the next turn.
|