Bump and publish a new version of the installer npm package (@weave-os/router, plus the legacy @workweave/router mirror). Use when asked to "bump the npm version", "publish a new npm version", or "deploy a new installer" after changes under install/ have merged to main.

Given a Codex **session ID**, pull the local rollout transcript (what the client saw) and the corresponding production cloud logs (which model/provider served it), then correlate them. The rollout `.jsonl` is ground truth for *what rendered*; the cloud logs confirm *what the router decided and what

Alias for force-model — pin this Codex session to a specific model through the Weave Router.

Pin this Codex session to a specific model through the Weave Router.

Pin the current parent thread to a model through the Weave Router while subagents route automatically.

Alias for router-feedback — submit feedback about a Weave Router decision or model performance.

Submit feedback about a Weave Router decision or model performance.

Route Codex through the Weave Router again (turn it back on).

Print the session id that correlates this Codex session in Weave Router telemetry and logs.

Show whether Codex is routing through the Weave Router or using its default provider.

> For an **automated** pre-merge regression net (fixture-driven, asserts caching/streaming/decision-headers against real Anthropic), run `make smoke` — see [docs/SMOKE.md](../../../docs/SMOKE.md). This skill is the interactive counterpart: stand the stack up by hand and drive it with `claude -p` t

Clear the active Weave Router model pin for this Codex session.

The `lsp` tool answers *semantic* questions through the language's own server: it resolves through imports, types, and aliases, where grep only matches text. Reach for it whenever the question is about a **symbol**; keep grep for plain strings, comments, and file types no server supports.