Overview & result
Tide introduces jev-router: a CLI that uses TypeSafe Jev to assess task difficulty and route between a fast model and a strong model. It keeps Claude Code's or Codex's login, tools, sessions and permissions, adding only a per-turn model-selection layer.
Show the original post (Japanese)
Claude CodeやCodexのモデル選びを、毎ターン手で切り替えていませんか？
jev-routerは、TypeSafeのJevでタスクの難しさを見て、速いモデルと強いモデルへ振り分けるCLIです。
各CLIのログイン、ツール、セッション、権限を維持したままルーティングだけを追加します。
https://t.co/uikQgcQ9gb
How Jev fits in the loop
- The CLI receives the new user turn before the upstream coding agent starts work.
- Jev classifies the task into a fast or strong model path.
- The selected upstream CLI continues with its native tools, session, and permissions.
How to reproduce
- Clone the verified repository and follow its Node.js installation steps.
- Launch the Claude Code or Codex wrapper with its existing login and permissions.
- Inspect the per-turn routing decision while keeping the upstream CLI interface unchanged.
Why this build matters
Model routing becomes a bounded assistant decision instead of another full generation step.
Limitations
- Routing quality depends on the task schema and thresholds chosen by the project.
- The post does not publish a controlled cost or accuracy benchmark.