Reconnect Codex through Weave Router using the managed configuration already saved on disk. It restores routing without running the installer again, and the change takes effect when Codex next starts.
Route Codex through the Weave Router again (turn it back on).
Review the instructions the agent will receive before you install.
When the user invokes $router-on, switch this Codex installation back onto
the Weave Router using the managed configuration already on disk.
Run exactly:
npx --package @weave-os/router -y -- weave-router on --codex{{SCOPE}}
Then report the result and tell the user the change takes effect on their next
codex launch — Codex reads its provider config at startup, so the current
session keeps routing as it already was. Do not re-run the installer or alter
any other Codex settings.
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 unexpected Claude Code output by matching a session’s local transcript with production router logs. Identify the serving model and trace response conversion code to explain empty blocks, tool output, or other rendering symptoms.
Investigate a Codex CLI session by matching its local conversation record with production router logs. Use the session ID to examine missing reasoning summaries, routing markers, unexpected models, or unusual tool calls and trace relevant code paths.
Switch Codex from Weave Router back to its normal provider for future sessions. Keep the existing login and router configuration, receive the command result, and retain the option to turn routing on again later.
Pin the current Codex session to a chosen model through Weave Router. This short alias accepts a model ID, runs the included script, and reports the router’s response while allowing the current turn to continue.
Pin the current Codex session to a specific model through Weave Router by providing its model ID. The skill applies the pin, continues the same turn, and reports the router's response.
Set up language servers, programs that help tools understand source code, for Go, TypeScript, Python, and Rust. Check missing prerequisites, install them with approval, and verify the lsp tool against a real source file.