chore(prompt-budget): ratchet limits after the session-todo cut - #6440
Conversation
…kill Reduce the prompt budget limits for the orchestrator and use_skill entries to reflect updated cost measurements, bringing them in line with current usage patterns. Auto-committed-on: macbook
Tiny Sweeper reviewTiny Sweeper reviewed this change across 6 lane(s) and found 0 active actionable finding(s). Detailed lane evidence and any incomplete work are listed below. State: Reviewing pending checks Review snapshot
Completeness: Complete What changedThe review could not produce a supported behavioral summary; inspect the cited changed surface and lane details below. FeaturesNone identified with supported citations. TestsNo supported feature-to-test mapping was produced. Test execution is not inferred. FindingsNo active actionable findings. Pending checks: Rust E2E (mock backend), Build Playwright E2E Artifact, E2E (Playwright / web lane), Desktop E2E (full suite, 3 OS), Rust Feature-Gate Smoke (gates off) Before merge
Agent review detailscritique
security
tests
commits
description
e2e
Evidence and run details
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughThe change lowers two prompt-budget ceilings in ChangesPrompt budget limits
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This narrowly scoped change updates prompt-budget ceilings to match the intended reductions, with no identified production impact or merge blocker. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
A rabbit checks the budget line, Comment ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
|
There was a problem hiding this comment.
tinysweeper found nothing blocking. Approving.
$0.0075 · 88,766 in / 4,844 out · 3,310 cached (4%) · ladder/vectors, gpt-5.6-luna, deepseek/deepseek-v4-flash · 56 embedded
critique: $0.0021 · 33,174 in / 515 out · 3,310 cached (10%) · gpt-5.6-luna
security: $0.0010 · 14,676 in / 163 out · 0 cached (0%) · gpt-5.6-luna
tests: $0.0015 · 15,604 in / 460 out · 0 cached (0%) · deepseek/deepseek-v4-flash
description: $0.0007 · 6,913 in / 496 out · 0 cached (0%) · deepseek/deepseek-v4-flash
e2e: $0.0017 · 16,559 in / 1,138 out · 0 cached (0%) · deepseek/deepseek-v4-flash
Why
#6436 merged with the last measured prompt/tool sizes not yet written back to
scripts/prompt-budget.limits: dropping the todo board tools shrank the orchestrator's tool column (20,946 → 20,434 B) and the shortenedtaskspack summary broughtuse_skillback under its line. Without this the budget lane reports "IMPROVED but was not ratcheted" and the saving can grow back.What changed
scripts/prompt-budget.limits:orchestrator:9169:20434,use_skillre-measured. Generated byscripts/check-prompt-budget.sh --write;scripts/check-prompt-budget.shis green.Verification
scripts/check-prompt-budget.sh→[prompt-budget] OK — every agent is within its limit.Summary by CodeRabbit
use_skilltool schemas.