feat: add response size limit with MAX_RESPONSE_CHARS env var (#125)#230
Open
JaydenB112 wants to merge 1 commit into
Open
feat: add response size limit with MAX_RESPONSE_CHARS env var (#125)#230JaydenB112 wants to merge 1 commit into
JaydenB112 wants to merge 1 commit into
Conversation
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
1 participant
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.
Addresses #125 - Addressed the response size detection with a
MAX_RESPONSE_CHARSenv variable that defaults to 50,000 to detect and truncate large responses before they exceed the LLM's context window. When truncated it provides users with a clear message to either adjust the limit or tighten the scope of their scrape. Still working on part two of this issue with an actual global setting to toggle between JSON and MD fetch though.