Skip to content
Agent Orchestration
Command

/router-models

List the models the Weave Router may route to, and turn them on or off.

From plugin
router
5.6k14 skills14 commands
$ npx -y skills add weave-os/router --agent claude-code

Command definition

router-models.md
description: List the models the Weave Router may route to, and turn them on or off.
argument-hint: [model or provider to enable/disable]
allowed-tools: Bash(npx:*)

Show me which models this installation lets the Weave Router pick from, and change that selection when I ask. This is the same list — and the same stored setting — as the checkboxes on the router dashboard's settings page.

Start by running:

`npx @weave-os/router models --claude{{SCOPE}}`

That prints every deployed model grouped by provider, with `[x]` for models the router may pick and `[ ]` for models it may not. Present it back to me as a compact checklist in that same `[x]` / `[ ]` form, keeping the provider grouping and the exact model ids — I select models by id.

Then:

  • If I named models or providers in `$ARGUMENTS`, work out whether I want them

on or off from how I phrased it, and apply it with `npx @weave-os/router models enable <id>... --claude{{SCOPE}}` or `npx @weave-os/router models disable <id>... --claude{{SCOPE}}` (add `providers` before `enable`/`disable` to switch a whole provider). Several ids can go in one call. Then re-run the list and show me the result.

  • If I named nothing, stop after the list and ask which ones I want to change.

Don't change anything I didn't ask for.

Other things I might ask for:

  • Rank models by preference:

`npx @weave-os/router models prefer <id> <id>... --claude{{SCOPE}}` (order matters), or `npx @weave-os/router models prefer clear --claude{{SCOPE}}` to drop the ranking.

  • Providers only: `npx @weave-os/router models providers --claude{{SCOPE}}`.

If the command reports that this router doesn't expose model selection, that's a Weave-hosted router: model selection belongs to the whole organization there, so tell me to change it at https://app.weaveos.com/organization/settings/weave-router/models — don't try to work around it. Its listing carries no on/off state, so present it as a plain list; don't infer which models are enabled.

Disabling a model takes effect on the router's next routing decision; no restart is needed.

Read more
@weave-os
Ships withrouter

Weave Router is a proxy that selects a model for each API request. It works with Anthropic, OpenAI, and Gemini APIs, so you can use it with coding tools or your own application. You can use the hosted router or run it yourself with your own provider keys.

Stars on GitHub

Momentum

stars in total
5.6k
Star history of weave-os/router on GitHub, a chart by star-history.com

Other commands on router.

fm

fm

Command

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

@weave-os@weave-osInstall Command
force-parent

force-parent

Command

Pin only this parent thread to a model while subagents route automatically.

@weave-os@weave-osInstall Command
models

models

Command

Alias for /router-models — list the models the Weave Router may route to, and turn them on or off.

@weave-os@weave-osInstall Command
rf

rf

Command

Alias for /router-feedback — submit feedback about router decision or model performance.

@weave-os@weave-osInstall Command

More commands from other plugins.

COMMAND_COMPLIANCE_REPORT

COMMAND_COMPLIANCE_REP…

Command

Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of: - `mcp__claude-flow__*` tools…

@ruvnet@ruvnetInstall Command
ask

ask

Command

This compatibility command keeps `/oh-my-claudecode:ask` available without loading the full `ask` skill description in every…

@yeachan-heo@yeachan-heoInstall Command
code-review

code-review

Command

Technical code review for quality, bugs, and AGENTS.md compliance

archon11d24k
@coleam00@coleam00Install Command