feat: cap rows returned to the agent context - #63
Merged
Conversation
execute_bigquery_sql now serializes at most MAX_CONTEXT_ROWS (1000) rows into the agent's context, so a large result no longer blows up the context. row_count reports the true total, and when the result is truncated a `truncated` flag plus `truncation_note` are surfaced so the agent knows it is seeing a prefix. The full result stays materialized in BigQuery and remains downloadable via query_ref. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
execute_bigquery_sql now serializes at most MAX_CONTEXT_ROWS (1000) rows into the agent's context, so a large result no longer blows up the context. row_count reports the true total, and when the result is truncated a
truncatedflag plustruncation_noteare surfaced so the agent knows it is seeing a prefix. The full result stays materialized in BigQuery and remains downloadable via query_ref.