Skip to content

tracking(runtime): finish provider-native web search #4330

Description

@Phoenix500526

Problem

#2152 established provider-hosted WebSearch for OpenAI Responses and Anthropic
Messages, but the remaining provider wires and verification gaps are split
between documentation and isolated issues or pull requests. There is no single
place to track ordering, shared invariants, and completion.

This is a coordination tracker. Existing provider-specific work remains
authoritative and should be linked rather than reopened.

Desired outcome

Every provider in the capability matrix has an explicit, fail-closed status.
Supported adapters execute search in the primary model request and preserve
provider events, citations, durable replay data, credential isolation,
privacy-mode removal, scoped tool ceilings, and explicit no-fallback behavior.

Checklist

Non-goals

  • Replacing Tavily or adding silent fallback
  • Inferring hosted search from generic protocol compatibility
  • Adding Z.AI's standalone Search API to the model-native path
  • Reopening work already owned by provider-specific issues or PRs
  • Provider-native Tool Search for large catalogs ([RFC] Provider-native Tool Search for large tool catalogs #1382)

Documentation

Activity

  1. wutongyuonce commented on Sep 8, 2026

    @wutongyuonce
    Contributor

    I'll take the Gemini grounding slice.

    Plan: attach provider-native google-search only for Gemini 3+, where @ai-sdk/google can mix googleSearch with function tools. Gemini 2.0/2.5 stay fail-closed (implemented: false) so Read/Write/Bash are not dropped. No Tavily fallback, no OpenRouter/generic-compatible inference.

    PR incoming, will link this issue.

  2. added theissue type on Sep 8, 2026
  3. added
    staleNo qualifying activity within the lifecycle policy window
    on Oct 9, 2026
  4. github-actions commented on Oct 9, 2026

    @github-actions

    This issue has had no human activity for 30 days and has been marked stale. It will be closed in 30 days unless someone comments.

    If the issue is still current, please confirm it against the latest main and add any information that would help move it forward. Assigned issues and issues labelled pinned are exempt from this policy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    staleNo qualifying activity within the lifecycle policy windowtrackingTracking or umbrella issue

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions