Before you press play
What you’ll find in the video
- Jev acts as a fast decision engine using three parallel question output types (choice, score, and boolean) rather than chat-based generation.
- A custom CLI router leverages Jev to select coding harnesses, target models, and reasoning budgets without manual switching.
- Session-level routing rather than per-message switching is used to preserve prompt caches and manage token consumption across planning and execution phases.
Worth knowing
Auto-generated English captions reviewed with Gemini. The custom routing CLI shown is a personal prototype requiring early-access API credentials, and its decisions reflect prompt heuristics rather than standardized router benchmarks.