feature: attribute tool-pruning savings — tokens and cost saved
Open
@huang195 is already working on this.
Since Sep 10, 2026.
enhancement
nice to have
- Dominant language
- Go
- Stars
- 13
- Forks
- 40
- Avg merge
- 12h 17m
- Merged PRs (30d)
- 156
Description
Feature Description
The README claims tool-definition pruning saves 4–20% of the prompt on every turn. Nothing
reports the realised figure, so the claim is currently unfalsifiable.
Proposed Solution
- Per request: tokens removed by pruning and the cost that avoided
- Rolled into session and per-model totals
- Distinguish savings from cache effects so the two are not double-counted
- Report per agent, and report zero honestly for agents with no tool inventory — do not
present "no savings" as "no data" or vice versa
Additional Context
Part of the Cortex v0.9.0 release, stretch scope. Note that toolscan/known.go hardcodes
Claude Code built-in tool names, so pruning currently applies to Claude Code only.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.