jev-codex-bridge
Local bridge where Jev selects model and reasoning effort for Codex Desktop and CLI, with a Windows service and cache-aware routing.
Overview
Jev Codex Bridge lets TypeSafe Jev select a model and reasoning effort for Codex Desktop and the Codex CLI, using your existing Codex login through a local bridge. On Windows it installs a background service with tested updates and rollback; on macOS and Linux you run it under your own supervisor. A policy file limits which models automatic selection may use, and you choose Jev Router in Codex to enable routing or a concrete model to choose manually; existing tasks can be attached by thread ID.
Routing selects a supported model-and-effort pair from task history and tool results, with the user's reasoning selection as a ceiling. It reassesses when user instructions or tool evidence change, reuses decisions for retries and continuations when evidence is unchanged, protects unfinished reasoning and observed cache reuse when reducing capability, keeps quality upgrades eligible, and falls back to the current pair if Jev is unavailable. TypeSafe receives routing text and model metadata, OpenAI receives the conversation, and decisions are stored locally. It needs Node 24+, has CI and is MIT licensed.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | Which model and reasoning effort pair should handle this Codex step? | — |
How it works
- Install the bridge and set allowed models
- Select Jev Router in Codex
- Jev picks model and effort from history and tool results
- Bridge reuses decisions when evidence is unchanged; protects cache
- Fall back to current pair if Jev is down
Strengths
- Respects user's effort ceiling
- Cache-aware downgrades
- Windows service with tested updates and rollback
Caveats
- Requires Node 24+ and Codex
- Routing text is sent to TypeSafe
Getting started
`npm install --global git+https://github.com/ansidium/jev-codex-bridge.git --ignore-scripts`, create ~/.jev-router.env, then `jev-bridge install`.At a glance
- Type
- CLI
- Status
- beta
- Language
- TypeScript
- Runtime
- local bridge service, CLI
- Has code
- yes
- Has tests
- yes
- License
- MIT
Use cases and integrations
How curated lists describe it
Model and reasoning routing for Codex Desktop and CLI, with a Windows service and validated updates.
hellogumbo/awesome-jev
Frequently asked questions
What does Jev decide?
The model and reasoning effort for Codex steps.
Will it override my effort setting?
No, your reasoning selection is the ceiling.
What if Jev is unavailable?
It keeps the current eligible pair or initial fallback.
Related projects
- jev-router★ 593
Per-turn model routing for Claude Code and Codex: wraps the real CLI and lets Jev send simple turns to fast models and hard ones to strong.
ProxybetaJavaScript - jev-codex-router★ 274
Per-call router for Codex where Jev picks the model and thinking effort for every model call, including tool continuations.
ProjectbetaPython TypeScript/Bun launcher that asks Jev which model and reasoning effort each Codex, Claude Code or Pi turn should use.
ProjectbetaTypeScriptGo CLI model router that uses one Jev analysis to recommend a model, harness and effort level, then selects deterministically.
CLIbetaGomacOS wrapper for Codex that lets Jev pick the model and reasoning effort for a thread, then pins that route.
ProjectbetaClaude Code and Codex plugin where Jev judges each turn for model routing, delegation, evidence search and compaction.
ProjectbetaTypeScript