🤖 perf: Token Budget rolls over again when a fresh window's own estimate already reaches the hard ceiling
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 66/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- backend
调研方向
Start with src/node/services/contextManagement/strategies/tokenBudget.ts, the file named in the issue, and trace how a rollover handles a fresh window whose estimate reaches the hard ceiling. Find the related tests and add coverage for the next send after that rollover. Done means it warns or blocks and does not roll over again.
由索引模型根据 Issue 内容生成。
描述
Split out of #5223 (its "Livelock guard" item). No fix is in the #5223 PR.
Problem
In Token Budget mode, a rollover starts a fresh context window. If that fresh window's own next-request estimate already reaches the hard ceiling, the next send rolls over again, and so does every send after it. Nothing stops the loop.
#5223 states the guard as: "when a fresh window's own estimate already reaches the ceiling, warn and continue or block instead of rolling over again."
Evidence (from #5223)
- Live UAT on a 60k window: one session fell into an 8-rollover livelock. The fresh window's own estimate (51.8k) reached the hard ceiling (51,808), so every send rolled over again.
- On a 200k window the fresh window is about 56k by estimate, so the livelock needs an unusually small window.
- Main has no guard for this today (checked in
src/node/services/contextManagement/strategies/tokenBudget.tsat 8c31fc7ac2).
Options
- Warn and continue: send the request without another rollover and show a warning that the window is too small for the fresh context.
- Block: refuse the send with an error that says the fresh context does not fit this model's window.
Acceptance
- Test: a fresh window whose own estimate reaches the hard ceiling does not roll over again on the next send. It warns or blocks, as chosen.
Refs #5223, #4858.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $523.18
- 主要语言
- TypeScript
- 星标
- 2.1k
- 派生
- 140
- 平均合并
- 5 小时 8 分钟
- 30 天内合并 PR
- 952
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
coder/xum 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
juice-shop/juice-shop#3706 ·
维护者通常 1 天内回复
-
sbx up from a subfolder silently pushes the whole work tree可能已有人在做 @pdettori 今天认领。 未关闭enhancement
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
outline/outline#14348 · 1 条评论 ·
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复