@alexeiled/claude-router 1.23.0 → 1.24.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.
@@ -283,6 +283,12 @@ and unpriced causes, not semantic success or task acceptance. A caller must eval
283
283
 
284
284
  ### Changes during a task
285
285
 
286
+ The route-table behavior below applies to the default `table` engine and to `shadow`. With opt-in `auto`, each
287
+ continuation reassesses context, images, availability and the cash cap; classifier reviews update demand, and observed
288
+ code or docs can end a bounded-execute discount. It does not use activity route-table moves. A tier pin retains its
289
+ demand for the turn but can be refitted when constraints change. If nothing fits, the native request runs with
290
+ `no-route-native`. See [automatic routing](configuration.md#routing-engine). Quality evaluation and cutover are pending.
291
+
286
292
  The classifier labels a turn from its prompt, and the work can change after that: a brief that reads as `ops` may turn into an hour of coding, and a hard fix may end in routine commands. The router therefore checks the route again while a task runs, for the tier and the activity, in both directions.
287
293
 
288
294
  - **On every later step of a turn** it reads the turn's tool calls. A turn labelled `ops` or `explore` that edits a code file moves at once to the tier's `code` route (`docs` when it edits only Markdown or `docs/` files). The tools are the evidence, so this needs no classifier support, and the cache cost does not hold it back; only the cash cap on a credits-billed model can. This move only goes up. The toast and the band show it as `↗ coding`.
@@ -334,13 +340,14 @@ On the **Classifier** tab, **ACROSS SESSIONS · since the last reset** shows the
334
340
  | **on** / **off** on the pane (`o` / `f`) | The same as `/router auto` and `/router off`. |
335
341
  | **pin** on the Now tab | Pin that tier for the next turn. Routing on must already be enabled. |
336
342
 
337
- A routing mode moves each tier's route one step toward cost or quality; pins and `micro` turns are not moved. The band and the Now tab show the mode and where it comes from, such as `cost (session)`. When the mode kept the cell's model and changed only its effort, as `cost` does for Opus at `high`, the band adds `effort only`: the cost estimates price the same tokens on both routes, so that change shows no difference there, though real output length can differ. A change applies from the next turn, and the route in use moves only through the usual checks, so on a running task a cheaper route can wait a few requests and for a checkpoint. **Mode** on the Policy tab sets the profile's mode. See [Routing modes](routing-modes.md).
343
+ With `table` or `shadow`, a routing mode moves each tier's route one step toward cost or quality; pins and `micro` turns are not moved. With opt-in `auto`, the mode changes the demand margin instead, and a tier pin uses exact demand without a margin. The band and the Now tab show the mode and where it comes from, such as `cost (session)`. When the mode kept the cell's model and changed only its effort, as `cost` does for Opus at `high`, the band adds `effort only`: the cost estimates price the same tokens on both routes, so that change shows no difference there, though real output length can differ. A change applies from the next turn, and the route in use moves only through the usual checks, so on a running task a cheaper route can wait a few requests and for a checkpoint. **Mode** on the Policy tab sets the profile's mode. See [Routing modes](routing-modes.md).
338
344
 
339
345
  ### Routing decisions
340
346
 
341
347
  Each routed turn adds rows to the session's decision record in `$.store` (`decisions:v1:<session id>`): one when the turn starts, one per classifier review or tool-based move inside it, and one when it ends. A row holds the prompt's origin (`composer`, `task-notification`, …, or `unknown`), the classifier's tier and activity with their shares, whether it counted as the running task, the tier, activity, route and reason chosen, and at the end the turn's tool bucket and how many replies were priced. It holds no prompt, tool or file text. The route is the one chosen, which is not always the one sent; see [Changes during a task](#changes-during-a-task). `/router decisions [n]` prints them. For a tier move or an activity move up, taken or held, the row also holds the probability mass the policy compared and the bar it compared it with, printed after the reason: `(upgrade-pending 52% vs bar 79%)`. A held move can show a mass above its bar: it then waits for a second vote or for a checkpoint. On `downgrade-pending` the mass is the support for the classifier's own choice; a tier between it and the running one can be closer to its bar. A `jump`, a move on the turn's own tool calls and a context or availability override show neither number. Each session keeps its newest 60 rows; records of the 20 most recent other sessions stay, for at most 30 days. **Delete history** deletes them all.
342
348
 
343
- A pin does not change the next turn after the pinned turn finishes. A fresh 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. A fresh session on any other model starts with routing off. `/clear` starts the new session with routing on. Resuming a saved session restores its saved routing on or off.
349
+ For `auto`, decision rows also show demand, target, outcome, move reason and a conditional next-turn cost estimate,
350
+ not measured savings. A tier pin does not change the next turn after the pinned turn finishes. With `table` or `shadow`, a fresh session starts with routing on for a model a tier routes to, or, with activity routing `on`, a model an activity override uses (Sonnet 5.5 on the defaults). With `auto`, any model in the configured catalog starts with routing on, even if no table route names it. A fresh session on any other model starts with routing off. `/clear` starts the new session with routing on. Resuming a saved session restores its saved routing on or off.
344
351
 
345
352
  ## Edit routes and policy
346
353