WebSearch: add date_after parameter to filter results by publication date

Resolved 💬 3 comments Opened Mar 25, 2026 by recessionalert Closed May 4, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When generating reports, every search must be filtered to a specific date window (e.g., past 3 days). Currently, WebSearch returns results of any age — the date filtering has to be done manually after results arrive, meaning stale content consumes context window tokens even though it will be rejected. A date_after parameter would
filter at the search level before results are returned, reducing context consumption and eliminating the need for post-retrieval date checking. Google's native after:YYYY-MM-DD operator already supports this — WebSearch should expose an equivalent parameter.

Proposed Solution

A date_after parameter would
filter at the search level before results are returned, reducing context consumption and eliminating the need for post-retrieval date checking. Google's native after:YYYY-MM-DD operator already supports this — WebSearch should expose an equivalent parameter.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

API and model interactions

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗