Jev Codex Model and Effort Router

Jev selects the model and effort for the first task in a Codex thread. That route stays pinned for later turns so the thread can reuse its model cache, greetings and other social messages do not set the pin, and an existing thread keeps its current model and effort when the version first sees it.

The README's quick setup is to paste one line into your coding agent: set up and verify the repository URL with default settings. If no key is available, the first codex start lets you add one, continue with normal Codex, or remove Jev; key input is hidden, validated, and saved in a user-only file.

Run jev-codex auth login, which lets you replace the saved key. Setup options also include --env-file PATH to read JEV_API_KEY from a file, alongside --no-wrap-codex, --no-shell, and --codex-path PATH for controlling the installation.

Yes: the default routing_mode is thread; set it to turn with jev-codex config set routing_mode turn so Jev selects a route before every turn. Routing frequency changes apply before the next turn, while preference, maximum effort, and pool changes apply when Jev next selects a pin.

On macOS, jev-codex settings launches a menu bar app where you choose the routing frequency, routing preference, maximum effort, and the model and effort pools. It is the GUI for the same settings the CLI exposes, and the README includes a screenshot of it.

Use remaining quota when routing is on by default: Jev receives the live Codex allowance, and high quota pressure selects the least intensive route that still meets the task's capability floor. Turn it off to route only by task needs and your routing preference.

Prerequisites are macOS and a Jev API key. The README documents setup flags and manual overrides but publishes no cost or accuracy benchmarks, and the GitHub metadata shows no license, so review the repository before depending on it in a workflow.