Tools2 min read

Google schedules a legacy Deep Research API agent shutdown for October 23: check your automation

Integrations using deep-research-pro-preview-12-2025 need a replacement check. This recalls the October 8 announcement, not a verified completed shutdown.

Prepared by the NADALI editorial team using AI

AI illustration: a hand replaces a teal segment in a loop of workflow cards beside a calendar without dates.
Nadali — original AI-generated editorial illustration created with OpenAI image generation · Original AI-generated illustration created for Nadali; use subject to applicable OpenAI terms; no exclusive copyright claim; no third-party input images used. · 1440 × 960

What is changing

Google has scheduled the shutdown of deep-research-pro-preview-12-2025 in the Gemini API for October 23, 2026. The company announced this on October 8; this article highlights the approaching date rather than a new announcement.

The deprecation table also lists October 23, but includes a general qualification: its dates are the earliest possible dates, and Google provides users with advance notice of the exact date. We have not tested the legacy agent and do not claim it has already been switched off. These sources do not specify a time of day.

Who should check

Small teams whose developer or employee has configured a research workflow through the Gemini API using that exact identifier. A weekly draft review of public sources is one illustrative scenario, not a tested business case.

This notice does not establish the shutdown of all Deep Research features or the Gemini app. First identify the service and version your workflow actually uses.

What to ask the person responsible

Google recommends changing the agent parameter in interactions.create requests to deep-research-preview-04-2026 or deep-research-max-preview-04-2026.

Nadali’s editorial checking sequence:

  1. Find the legacy identifier in integration settings and scheduled jobs. Identify an owner for each workflow.
  2. Check access to the selected replacement and its current billing terms before running a test.
  3. Run an approved test using non-confidential material, without sending results to customers or changing business records.
  4. Check task completion, source links and whether the next workflow step can read the returned result.
  5. After an approved change, verify the next scheduled run. Keep a manual way to prepare the required review until the workflow is confirmed working.

Changing a configuration string does not establish that the whole workflow works correctly. An acceptance test set can help compare results.

Availability and limits

Current documentation describes both replacements as preview versions using the Interactions API. Tasks run in the background; charges depend on the underlying models and tools used. Similar names do not establish equal cost or complete compatibility.

Nadali checked public sources on October 22, 2026, but did not make API requests, test your account or measure quality or cost. The practical takeaway is to check the specific dependency before the scheduled shutdown and obtain evidence that the complete workflow works.

Author: Nadali. Prepared with AI. Cover: an original conceptual AI-generated illustration, not an interface screenshot or evidence of testing. 

Sources and verification

  1. Google Gemini API release notes: October 8, 2026 legacy Deep Research agent deprecation ↗
    Source checked: 2026-10-22
  2. Google Gemini API deprecations: managed agents and date qualification ↗
    Source checked: 2026-10-22
  3. Google Gemini Deep Research agent: current versions, execution and pricing ↗
    Source checked: 2026-10-22