Elune Coding Agent Switch
这是 elune 公开的项目资料。本站按原始来源展示项目信息，用中文说明适用场景和阅读边界；项目名、源帖与代码保持原样，便于逐项核对。
这条案例记录了什么
编码 Agent、Agent 与模型路由、安全与权限门禁
对模型选择、片段可见度或工具风险提供有界判断。
社区公开项目或作者演示
原始来源：First-hand configuration post and demo by @elune0x。作者自述，本站未独立复现。
elune
记录日期：2026-09-24。日期与身份应以原始资料为准。
原始演示视频
视频来自此案例记录的原始媒体；播放内容和作者声明不等于本站复现。
怎样核对这个项目
- 先打开原始来源，确认作者、日期与 Jev 在项目中的具体用途。
- 如果提供仓库，再检查代码、运行要求和许可证；仓库存在不代表本站已经运行成功。
- 对速度、成本、准确率和规模数字，查看原文的任务、环境和计算口径。
- 仓库状态和测试是否完整。
- 敏感命令的程序门禁。
- 完整任务的费用与结果。
- 路由候选是否完整。
原始文字与技术细节
以下内容保留原语言，供核对事实。中文页的场景说明是阅读提示，不是逐句翻译或实测结论。
展开英文项目摘要与原帖
项目摘要
Elune demonstrates a setup in which Jev selects Claude Code or Codex for a task and supplies typed decisions before risky tool execution. The post describes shadow logging followed by an enforce mode, while the implementation repository remains unverified.
来源原文
Jev just made the Claude Code vs Codex debate obsolete I connected both to Jev - now the best coding agent is selected for every task, and neither can cross a risky tool boundary without a typed decision in one run it scanned 247 files, routed the security audit to Claude Code, routed the patch to Codex, passed 18/18 tests and stopped npm publish before execution here’s how to set it up in 10 min: task → Jev decision → Claude Code / Codex → tool execution → fresh verification step 1 → open @typesafeai and create your Jev API key (never paste it into chat) step 2 → clone and verify the complete agent switch step 3 → export the key before starting either agent: export TYPESAFE_API_KEY="YOUR_KEY" step 4 → test the full decision layer before connecting a live agent: npm run doctor && npm run check:claude && npm run check:codex step 5 → connect Claude Code directly from the repository: claude --plugin-dir . Claude discovers the plugin and turns Jev review decisions into real confirmation requests step 6 → for Codex, install the same folder through your local plugin marketplace, open /hooks and trust the exact PreToolUse hook Codex uses the same policy and safely stops calls that need human review step 7 → keep agent: auto and the plugin detects Claude Code or Codex automatically - or set agent: claude / codex when you want to lock one runtime step 8 → start in shadow mode for 20–50 real decisions: export JEV_AGENT_SWITCH_MODE="shadow" && export JEV_AGENT_SWITCH_LOGGING="true" your agent keeps working normally while Jev records the route, confidence and outcome without blocking anything step 9 → switch to enforce only after the decisions look reliable: export JEV_AGENT_SWITCH_MODE="enforce" safe calls pass, uncertain calls stop for review, dangerous calls are denied the default boundary is 0.62 minimum confidence and 0.86 harmful-action probability step 10 → use it normally - ask Claude Code or Codex to inspect, patch, test or prepare a release; the same Jev layer stays in front of both the result: Claude Code handles deep repository context, Codex handles fast patches and verification, and Jev decides which worker gets the task - while keeping publishing, production and irreversible actions behind a human boundary unfortunately, most people are still comparing coding models as if one model needs to win forever the actual 2030 setup makes the model replaceable: one task enters, Jev selects the best worker, code enforces the decision and every action leaves a receipt Steal the agent setup everyone will use by 2028, copy the repo below - then read the full Jev Engineering playbook ↓
原记录的限制
- The author refers to a repository but no matching public repository was verified; no GitHub button or copy-and-run instructions are provided.
- The reported run, thresholds and security behavior have not been independently tested.