The Stable channel has been updated to 150.0.7871.100/.101 for Windows and Mac and 150.0.7871.100 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log

Earlier this year, we announced Fill with Gemini in Google Sheets, a new AI-powered feature designed to make data preparation and manual entry even easier. Leveraging the capabilities of the AI function in Google Sheets, Fill with Gemini eliminates the need for complex formulas, helping you easily generate text, summarize information, categorize data, or analyze sentiment at scale with generated content appearing directly in the cells you choose.

Previously available in English, Spanish, Portuguese, Japanese, Korean, French, Italian, and German, both Fill with Gemini and the AI function are now expanding to users in Mandarin, Dutch, Malay, Hebrew, Polish, Turkish, Czech, Indonesian, Swedish, Danish, and Norwegian.

Getting started

• Admins: Fill with Gemini is an entry point to the existing AI function. It will be hidden if the Smart features for Google Workspace setting is disabled. Visit the Help Center to learn more about managing Google Workspace smart features for your users.
• End users: You must have Workspace smart features enabled to use Fill with Gemini. Users can trigger Fill with Gemini by dragging a selection or selecting empty cells to see the prompt menu. Visit the Help Center to learn more about filling columns with Gemini.

Rollout pace 

• Rapid Release and Scheduled Release domains: Gradual rollout (up to 15 days for feature visibility) starting on July 7, 2026

Availability

• Business: Business Standard and Plus
• Enterprise: Enterprise Standard and Plus
• Consumer: Google AI Pro and Ultra
• Education Add-ons: Google AI Pro for Education
• AI Add-ons: AI Expanded Access*

*Starting July 15, 2026, users with AI Expanded Access licenses will have higher limits on usage of Fill with Gemini and the AI function in Sheets. 

Resources

• Google Docs Editors Help: Use the AI function in Google Sheets
• Google Admin Help: Set smart features & controls on or off for users

Three new FireSat satellites have launched, expanding a network that uses Google AI to help fire agencies detect early-stage wildfires.

Occupancy counting is now available for Android-based Neat room hardware to help measure how meeting rooms are used. This feature brings the same occupancy counting capabilities found on ChromeOS devices to Android-based hardware.

Understanding room occupancy helps organizations optimize real estate and room design based on user needs. For instance, organizations can track if rooms with older video hardware are being avoided in favor of rooms equipped with better tracking cameras and audio bars.

Admins can review occupancy data in the Google Admin console and optionally download it as a spreadsheet. This feature does not collect or store any personally identifiable information (PII). Because occupancy detection processes data locally on the device, the camera LED indicator may remain off during counting depending on the hardware vendor. Refer to vendor documentation for device-specific information.

Review room booking and occupancy in the Admin console

Getting started

• Admins: This feature will be off by default and can be enabled at the domain, organizational unit (OU), or group level. Visit the Help Center to learn more about turning on occupancy detection.
• End users: There is no end-user setting for this feature.

Rollout pace

• Rapid Release and Scheduled Release domains: Extended rollout (potentially longer than 15 days for feature visibility) started on July 6, 2026

Availability

• Available to all Google Workspace customers with Google Meet on Neat AOSP hardware devices. 

Resources

• Google Workspace Admin Help: Turn on occupancy detection
• Google Workspace Admin Help: Track room and device usage with Meet hardware

Today, we are launching a pilot process to expedite the Basic Access application review process. If you have a pending Basic Access application for your Google Ads API developer token, then you can complete brand verification for your Google Cloud project to expedite the reviews for your pending application. With this launch, we aim to reduce the review delays and better meet the significant interest from our developer community for Google Ads API access.

What is brand verification?

Brand verification provides a way for an application developer to verify that they accurately represent their identity and intent as specified by Google API Services User Data Policy. Brand verification is part of the OAuth App verification process, and is an automated self-service option for most developers.

How do I expedite the review process?

If you have a pending Basic Access application for your developer token, then follow these instructions to expedite the review process:

1. Associate your developer token to your Google Cloud project. This step is important; without it we won’t know which Google Cloud project to use as part of the review process.
2. Complete brand verification for your Google Cloud project. If you completed brand verification for your Google Cloud project in the past while using another Google API, you don’t need to repeat the process. If you have more than one Google Cloud project associated with your developer token, you need to complete brand verification only for one project.

Once your Google Cloud project is brand verified, your pending Basic Access application will be reviewed in the next few hours.

Is brand verification mandatory?

Currently, brand verification is optional and is used only as a signal for faster determination of Ads API Basic Access eligibility. This means that

• You may complete the Brand verification process for your Google Cloud project to expedite the review process for your Basic Access application.
• The Google Ads API Compliance team may request some developers with pending Basic Access applications to complete brand verification.

You don’t need to complete brand verification if you already have an approved developer token and aren’t newly applying for Basic Access level.

We will closely monitor the developer experience throughout pilot surveys and use that data to determine the future changes to the application review process for developer token access levels.

 - Anash P. Oommen, Google Ads API Team

We’re announcing new capabilities in Managed Agents in Gemini API so developers can build reliable, production-ready agents.

Content creators and publishers use many channels beyond their own websites to reach their audiences. As people gravitate toward firsthand perspectives and different content formats, we want to make it easier for site owners and creators—even those without their own website—to get a consolidated view of how all of their content is getting discovered on Search.

The ChromeOS Stable channel is being updated to OS version 16667.61.0 (Browser version 149.0.7827.232) for most ChromeOS devices.

1. File a bug

2. Visit our ChromeOS communities

1. General: Chromebook Help Community

2. Beta Specific: ChromeOS Beta Help Community

3. Report an issue or send feedback on Chrome

4. Interested in switching channels? Find out how.

Luis Menezes

Google ChromeOS

Google Mobile Ads (GMA) Next-Gen SDK is now the preferred SDK for Android development with Google AdMob and Google Ad Manager. GMA Next-Gen SDK is a significant rewrite of Google Mobile Ads SDK that improves speed, stability, and the developer experience. Google Mobile Ads SDK for Android is now legacy.

We invite you to integrate GMA Next-Gen SDK and discover the performance and stability enhancements it can bring to your Android applications. To get started today, migrate to GMA Next-Gen SDK in AdMob and Ad Manager.

Deprecation of Google Mobile Ads SDK (legacy)

Google Mobile Ads SDK (legacy) versions 25.x.x are now considered outdated by GMA Next-Gen SDK. Version 25.x.x follows a similar deprecation schedule, as previous major versions. See the following timeline for support of Google Mobile Ads SDK (legacy) version 25.x.x:

Date	Google Mobile Ads SDK (legacy) status
July 1, 2026	Supported Ads continue to serve. Technical support is available through the contact us form.
June 30, 2027	Deprecated Ads continue to serve. Technical support is no longer available.
June 30, 2028	Sunset Ads are at risk of not serving. Google Mobile Ads SDK (legacy) is reported as outdated and prevents app releases.

For more information about the deprecation timelines and definitions, see the deprecation schedule.

Migrate with an AI skill

We recently introduced agent skills, including a google-mobile-ads-android-migrate-to-next-gen skill to help you migrate your app from Google Mobile Ads SDK (legacy) to GMA Next-Gen SDK.

For details about migrating to GMA Next-Gen SDK with AI, see Migrate with AI tools.

Additional Resources

• Integration guide: The latest version and setup instructions are available in our Set up GMA Next-Gen SDK guide in AdMob and Ad Manager.
• Migration guide: Instructions to migrate to GMA-Next Gen SDK in AdMob and Ad Manager.
• Developer samples: Example applications are available in the gma-next-gen-sdk-android-examples GitHub repository.

If you have any questions or need additional help, contact SDK support. To discuss this post or engage in community discussion, join the GMA Next-Gen SDK channel on our Discord server to share your thoughts.

 - Natalia Vargas-Caba, Mobile Ads Developer Relations

Distributed AI training is notoriously fragile because losing a single machine typically crashes the entire multi-node job, forcing a time-consuming, full-workload infrastructure restart. To address this, Google’s JAX ecosystem utilizes elastic training via Pathways, which converts a hardware failure into a catchable Python exception so the running process can survive. When an unplanned failure occurs, the system automatically replaces only the broken worker, restores the last viable checkpoint from Cloud Storage, and resumes training in place—minimizing total downtime to under two minutes without ever restarting the main controller process.