DEMO / RECORDING
Overview & Result
Gavin's open-source Codex wrapper asks Jev to select a model and reasoning effort for a task. The repository clarifies that default routing is once per thread, with optional per-turn routing.
How Jev fits in the loop
- A Codex task reaches the wrapper.
- Jev chooses a model and effort level from configured pools.
- Codex runs with that selection; default thread mode pins it to preserve model cache.
How to reproduce
- Use the repository's documented macOS setup and provide a Jev API key.
- Start a new Codex thread and observe the initial model-and-effort choice.
- Compare thread-pinned and optional per-turn routing according to the README.
Why this build matters
The repository exposes a concrete routing frequency and cache tradeoff that the short demo post does not explain.
Limitations
- The current README says Jev normally selects for the first task and pins the route for later turns; per-turn routing is opt-in. Do not read the X post as proof that every turn is rerouted.
- macOS and a Jev API key are required.