JevForAgents中文English
Agent 与模型路由 · Agent 评估

Token Saver

这是 ⭕ AI & Design (Marco) 公开的项目资料。本站按原始来源展示项目信息,用中文说明适用场景和阅读边界;项目名、源帖与代码保持原样,便于逐项核对。

这条案例记录了什么

场景

Agent 与模型路由、Agent 评估

根据任务状态选择一条已定义的处理路径。

证据

社区公开项目或作者演示

原始来源:Original X post and GitHub repository。尚未独立核实。

时间与作者

⭕ AI & Design (Marco)

记录日期:2026-09-21。日期与身份应以原始资料为准。

怎样核对这个项目

  1. 先打开原始来源,确认作者、日期与 Jev 在项目中的具体用途。
  2. 如果提供仓库,再检查代码、运行要求和许可证;仓库存在不代表本站已经运行成功。
  3. 对速度、成本、准确率和规模数字,查看原文的任务、环境和计算口径。
  4. 路由候选是否完整。
  5. 模糊请求的回退分支。
  6. 完整任务成本与结果。
  7. 是否有可观察的正确答案。

原始文字与技术细节

以下内容保留原语言,供核对事实。中文页的场景说明是阅读提示,不是逐句翻译或实测结论。

展开英文项目摘要与原帖

项目摘要

The author keeps Astra in charge of planning, difficult decisions, review, and integration; Muse performs bounded coding work; Jev Context selects relevant excerpts before context reaches the main coding agent.

来源原文

I did a thing! I got sick and tired of my Codex tokens draining faster and faster lately. Then I realized Meta’s Muse 1.3 at max reasoning is surprisingly close to Sol on coding benchmarks, but way cheaper to run. I'm on the $15 plan and I think it will be very hard for me to use all the tokens it's allowing. So I made something to save Codex tokens. It’s called Token Saver. It adds two skills and a set of instructions to Codex so it can delegate work to Muse and be more selective about what goes into its context. You keep using Codex, with Astra in charge. In my setup, Astra handles planning, difficult decisions, review, and integration. Muse takes bounded assignments like investigating a bug, implementing a feature, making repetitive edits, or writing tests. It returns a compact handoff for Astra to check against the actual code. Small tasks stay with Astra when delegation would create more work than it saves. Then there’s Jev Context, the other half of this. Before dumping entire files or huge logs into Codex, it helps select the excerpts relevant to the task. Those excerpts keep their file paths and line references, and the originals remain available when more context is needed. Filtering runs locally by default. You can optionally enable TypeSafe’s Jev API to rank excerpts by meaning rather than just keyword overlap. The idea is pretty straightforward: let Astra make the important decisions, let Muse do useful work without filling up the main conversation, and avoid making Codex read a mountain of material it doesn’t need. I also added isolated Git worktrees for edits, checks for out-of-scope changes, resumable worker sessions, and an optional usage and acceptance ledger. A worker saying “done” still needs review. Actual savings will depend on the task and the review overhead. Delegation moves some usage to Meta, so fewer Codex tokens won’t necessarily mean fewer tokens overall. The goal is to make my Codex allowance go further without handing every decision to a cheaper model. Built it for my own workflow. Put it on GitHub so you can use it too. https://github.com/TheMarco/token-saver

原记录的限制

  • The post does not report an independent token-savings or accuracy benchmark for Jev Context.
  • Delegation quality depends on the task boundary and on the primary agent reviewing the handoff.
  • Filtering context must not remove instructions, paths, or error details required for safe execution.

继续浏览

返回中文案例目录 · 阅读相关应用场景