Alias for force-model — pin this Codex session to a specific model through the Weave Router.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
When the user invokes $fm <model-id>, run this skill's scripts/emit.sh using the
absolute path shown in this skill's <path> (its directory + /scripts/emit.sh).
Pass the model id as arguments, quoted as a single argument list.
Do not send a user message and do not type a Codex slash command.
The script prints a leading-space /force-model line. The Weave Router reads that
exec output, pins the session, and continues this turn — so run the script once and
do not repeat its output as your answer. Then report the router's response.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Investigate a specific Claude Code session by session ID — correlate the local transcript (`~/.claude/projects/...jsonl`) with the router's production logs to understand what the client rendered vs. what the upstream served. Use when given a session ID and asked "why did X render?" for a Claude Code conversation routed through the router.
The English summary is being prepared. Showing the original description.
Investigate a specific Codex CLI session by session ID — correlate the local rollout transcript (`~/.codex/sessions/YYYY/MM/DD/rollout-*-<SESSION_ID>.jsonl`) with the router's production logs to understand what Codex rendered vs. what the upstream served on the /v1/responses path. Use when given a session ID and asked "why did X render?" (missing thinking, missing routing marker, wrong model, tool-call weirdness) for a Codex conversation routed through the router.
The English summary is being prepared. Showing the original description.
Switch Codex back to its normal provider for future sessions.
The English summary is being prepared. Showing the original description.
Pin this Codex session to a specific model through the Weave Router.
The English summary is being prepared. Showing the original description.
Install language servers (gopls, typescript-language-server, pyright, rust-analyzer) and their prerequisite toolchains (Go, Node/npm, rustup) so the lsp tool works. Use when the user asks to enable or install LSP / language-server support, when lsp_enable reports a missing toolchain, or when the lsp tool reports no language server is installed.
The English summary is being prepared. Showing the original description.
Recipes for the lsp tool — resolving where a symbol is defined, every place it is used, type signatures and docs, file outlines, and compiler/type errors through a real language server (Go, TypeScript/JavaScript, Python, Rust). Use when navigating or explaining code by symbol, finding callers or usages, checking what broke after an edit, or deciding between lsp and text search.
The English summary is being prepared. Showing the original description.