Add maxAgeHours parameter to ContentsOptions #123
Merged
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
LiamHz
force-pushed
the
lh/add-maxAgeHours
branch
from
10cc970 to
1e81e1c
Compare
Max age in hours for cached content. 0 = always livecrawl, -1 = never livecrawl (cache only). Cannot be used together with the livecrawl parameter. Co-Authored-By: Claude Opus 4.5 <[email protected]>
LiamHz
force-pushed
the
lh/add-maxAgeHours
branch
from
1e81e1c to
05545c8
Compare
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
maxAgeHourstoContentsOptionstype and the contents option extraction logic0= always livecrawl,-1= never livecrawl (cache only)livecrawlCompanion to exa-labs/monorepo#14546 which renames the server-side parameter.
Test plan
npm run build)🤖 Generated with Claude Code