Budget-aware retrieval: oversized filtering, MMR budgeting, chain output budgeting#148
Merged
gvonness-apolitical merged 2 commits intomainfrom Mar 4, 2026
Merged
Conversation
…g, chain output budgeting Retrieval pipelines now enforce token budgets at multiple stages instead of only at final assembly. Oversized chunks (individually > maxTokens) are filtered before MMR in search and passed through without scoring in chains. MMR tracks remaining budget during greedy selection. Chain formatting drops chunks that would exceed the remaining budget. Version bump to 0.9.2.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
maxTokensare excluded a priori — filtered before MMR in search, and passed through (but not scored) in chain walking so the chain doesn't break at large nodesTest plan
npm run build && npm test— 2038 tests passsearch max_tokens:500with large chunks in memory → no chunk exceeding 500 tokens in responserecallthrough a chain containing an oversized node → chain continues past it, node excluded from output