gemini_investigate: raise hard step cap from 10 to 20 - #14
Merged
Conversation
…emini API rejects role 'function')
…o investigations can actually read page content (previously only notion_search/notion_query_database were available)
… Compute defaults to a 300s function timeout, giving far more headroom than the original 10-step cap assumed
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.
Raises
gemini_investigate'sHARD_MAX_STEPSfrom 10 to 20.The original cap was conservative due to a stated concern about Vercel's serverless function duration limit. As of April 2025, Vercel enables Fluid Compute by default for all new projects, which raises the default function timeout to 300 seconds — this project (connected Jul 19, 2026) is almost certainly already on that default. At an estimated 5–10s per investigation step, 20 steps comfortably fits within that budget with margin to spare.
Also updates the
max_stepsparam description intools.jsto reflect the new cap.