docs(agent): add guidance on output size limits for large result sets#735
Open
firecrawl-spring[bot] wants to merge 1 commit intomainfrom
Open
docs(agent): add guidance on output size limits for large result sets#735firecrawl-spring[bot] wants to merge 1 commit intomainfrom
firecrawl-spring[bot] wants to merge 1 commit intomainfrom
Conversation
Document that a single agent run typically returns ~100-200 rows of tabular data due to LLM output token constraints, and recommend splitting large extraction tasks into multiple focused runs. Co-Authored-By: micahstairs <micah@sideguide.dev>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
Adds a short "Large Result Sets" section to the Agent documentation (
features/agent.mdx) explaining that a single agent run typically returns ~100–200 rows of structured tabular data due to LLM output token constraints, and recommends splitting large extraction tasks into multiple focused runs.This was a recurring support question where users assumed the row limit was a plan restriction.
Related Pylon Ticket
https://app.usepylon.com/issues?issueNumber=24762
Test plan