Pin this Codex session to a specific model through the Weave Router.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
When the user invokes $force-model <model-id> (or $fm), 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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Switch Codex back to its normal provider for future sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Alias for force-model — pin this Codex session to a specific model through the Weave Router.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。