Magpie switches agent models from the menu bar, and could host a Jev layer
Magpie uses one local gateway to unify model selection across Claude Code, Codex and other agents, and the author argues it already sits where a Jev layer should route calls on demand.
THIS MENU-BAR APP PUTS CLAUDE CODE ON KIMI IN ONE CLICK. 1,730 GITHUB STARS IN A WEEK, AND IT'S HALF OF WHAT THIS ARTICLE DESCRIBES magpie lists every agent on your machine and the model it runs on. claude code, codex, gemini cli, opencode, cursor. click a value, pick a model. under the hood it runs one local gateway that speaks the openai and anthropic apis, so every agent points at 127.0.0.1 and picks from one catalog. the article routes per decision: code → Jev → Kimi K3 → you magpie routes per agent. you pick the model once and every call pays that price, the easy ones included. that's the part i care about: magpie already sits between every agent and every model, which is where a jev layer would decide which calls actually need kimi.
This post quotes another post: x.com/polydao/status/2104783226833186920