Codex CLI with RouterLab
A ScioNos path from installation to your first call. Available models depend on your access and wrapper version.
1. Check prerequisites
Node.js ^22.13.0 or ≥23.5.0, installed Codex CLI (≥0.144.1) and an active RouterLab key. On Linux, persistent secure storage requires secret-tool and an available Secret Service. Check your ScioNos version’s README for its requirements.
Terminal shell
node --version
codex --version2. Install ScioNos and connect your key
Use the routerlab service. Login requests your key through a masked prompt. Keep it out of published commands. Diagnostics should confirm connectivity and a non-empty authorized catalog.
Terminal shell
npm install -g wrapper-scionos
wrapper-scionos --version
wrapper-scionos auth login --service routerlab
wrapper-scionos doctor --service routerlab3. Choose your model and launch
Codex uses the Responses protocol. In the native /model picker, choose a model offered by ScioNos and authorized by your key. Presence in the general catalog does not prove Responses compatibility. Trial accounts must choose a compatible -trial variant.
Terminal shell
wrapper-scionos codex launch --service routerlab4. Complete your first launch
Open a test folder. Ask for a short answer without tools, then an authorized file read. You should receive a response and see usage in RouterLab. Exact output depends on the model.
Test prompt text
Reply “connection successful”, then read this folder’s README and summarize it in one sentence. Do not modify any files.Limitations and troubleshooting
401: log in with your key again. 403 or empty catalog: check the plan, expiry and authorized models. 429: all keys and models share the quota; check your budget and reset. Fix a rejected subagent with an authorized model. Do not replace a Trial variant with a production route to bypass a rejection.
Tools, vision, streaming and reasoning depend on the model and protocol. Validate a small representative case before your project. Service destinations are fixed; custom base URL variables do not replace them.
Diagnostics shell
wrapper-scionos doctor --service routerlab
wrapper-scionos auth status --service routerlabLogout and restore
Exit Codex, restore the configuration backed up by ScioNos, then log out if you want to remove the stored key.
Terminal shell
wrapper-scionos codex restore --service routerlab
wrapper-scionos auth logout --service routerlab