Chrome for Android Update

 Hi, everyone! We've just released Chrome 152 (152.0.7977.64) for Android. It'll become available on Google Play over the next few days. 

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.


Android releases contain the same security fixes as their corresponding Desktop releases (Windows & Mac: 152.0.7977.64/65, Linux: 152.0.7977.64) unless otherwise noted.

Krishna Govind

Beta Channel Update for ChromeOS / ChromeOS Flex

The Beta channel is being updated to OS version 16765.31.0 (Browser version 152.0.7977.63) for most ChromeOS devices.

If you find new issues, please let us know one of the following ways:


  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

Quick Read: see how a paper answers your question

Answering a research question often requires reading through several papers and figuring out how each of them might be useful. You need to track down what each paper says about your question, what methods the authors used to arrive at the relevant results, and what caveats to keep in mind to understand the boundaries.

Today, we are introducing Scholar Quick Read, to help you answer your research queries faster. Search results in Scholar Labs and Scholar search that discuss your question in depth now include a “Quick read” link.

Click “Quick read” to read a short presentation of the paper focused specifically on your query. You’ll see an overview and three sections: Answers, Approach, and Considerations.

The Answers section presents an overview of what the paper says about your query as well as the supporting details for each of the points. Click “Show details” to view the details.

The Approach section describes the methods and techniques from the paper that are relevant to your question.

Finally, the Considerations section lists some caveats to keep in mind as you analyze the results.

Quick Read links appear only for papers that you have access to. We have worked with many of our scholarly publishing partners to enable them for your subscribed articles. We thank all our colleagues for joining us in this shared endeavor.

Quick Read is available for logged in users and is currently limited to English articles.

Here is hoping Quick Read helps find answers to your research questions in the ocean of knowledge.

Control “Take notes for me” directly from Google Meet hardware touch controllers

On August 31, 2026, we’ll start rolling out the ability to start, stop, and manage the “Take notes for me” feature directly from the Google Meet Hardware touch controller for eligible meetings. This ensures in-room participants have direct control over Gemini note-taking without being in Companion mode.



Controlling “Take notes for me” from the Google Meet hardware touch controller


Historically, managing AI features during a meeting required a user to join from a laptop in Companion mode. This new update surfaces the necessary controls directly on the touchscreen hardware, making it easier for team collaboration. In particular, it offers the following:

Easy visibility & control

We are surfacing a dedicated badge on the touch controller screen, mirroring the web experience. Users can easily see if Gemini is taking notes and toggle its state between active and inactive.



Active and inactive states of “Take notes For me” on the Google Meet hardware touch controller


Off-the-record capability

Users can confidently pause note-taking during off-the-record discussions, then resume with the tap of a button.



Pause and continue taking notes when needed with “Take notes For me” on the Google Meet hardware touch controller


Note: This feature will be available on the touch controller only for meetings where “Take notes for me” is available.

Getting started

Rollout pace

Availability

  • Business: Business Standard and Plus
  • Enterprise: Enterprise Standard and Plus
  • Consumer: Google AI Plus, Pro, and Ultra
  • Other Editions: Frontline Plus
  • Education Add-Ons: Google AI Pro for Education

Note: The plans above include “Take notes for me,” but this feature only operates on Google Meet hardware, which requires a separate license. Some users on Google Meet hardware with licenses that do not include “Take notes for me” functionality may see this feature if they join a meeting that is “Take notes for me’“ capable.

Resources

Google Ads API Developer Assistant v4.0.0

A major release of the Google Ads API Developer Assistant is now available. This release transitions the assistant from a standalone project setup to a unified plugin architecture designed to bring specialized Google Ads API capabilities directly into AI agent workflows.

What is it?

The Google Ads API Developer Assistant brings deep Google Ads domain expertise into AI coding environments like Antigravity and Claude Code. It equips your AI assistant with specialized tools and guardrails. Functions include:

  • Generate idiomatic code: Create tested, best-practice integration code across Python, Java, PHP, .NET, and Ruby.
  • Validate GAQL queries: Automatically verifies syntax, field compatibility, date segmentation, and zero-impression rules before running queries.
  • Inspect Protobuf schemas: On demand discovery of resource fields, data types, and enum definitions for any active Google Ads API version to ensure that GAQL query fields are valid.
  • Troubleshoot API issues: Diagnose offline conversion upload failures, navigate manager account hierarchies, and construct Performance Max listing filters. You can pose natural language questions like “Show me all the ads in my account with problems and recommend how to fix them.”
  • Answer API questions: The assistant answers questions by combining embedded Google Ads API architectural rules with dynamic, local Protobuf schema inspection to deliver version-accurate guidance and verified code snippets. It grounds its responses directly in official API definitions and client library source code rather than relying solely on general model training. An example question might be, “What is a shared set and how do I use it?”
  • Adhoc reporting: You can ask for performance data in plain English, and the assistant instantly constructs, validates, and runs the required GAQL queries directly against your Google Ads account. It streams live results back into your chat as clean, formatted tables, making ad hoc reporting and metric investigations effortless. If you want to save the results, ask it to “Save results as a CSV file in <your directory>” and you can load it into a spreadsheet for analysis.

Support for Antigravity and Claude Code

This release introduces dual-platform support:

  • Antigravity: Native support for Antigravity developer environments with global and workspace plugin registration.
  • Claude Code: Full integration with the Claude Code CLI plugin system, including custom slash commands (such as /validate-gaql, /inspect-object, /troubleshoot-conversions, and /get-cids).

Unified installation scripts are available for Linux, macOS (bash), and Windows (PowerShell) to provide consistent lifecycle management across all three platforms.

Improved performance

  • Reduced token consumption: Progressive disclosure of rules and schemas loads only the context needed for a given task, reducing prompt token overhead.
  • Faster response times: On-demand skill execution and targeted command routing deliver faster end-to-end task completion.
  • Lower CPU utilization: Streamlined execution pipelines eliminate background process overhead during development sessions.
  • Reduced disk I/O: Reducing the number of unneeded files in the plugin tree prevents file watchers, linters, and IDE indexers from scanning tens of thousands of unused protobuf/SDK files.
  • Lower memory (RAM) footprint & zero daemon overhead: Skills and commands now run ephemerally as fast child processes only when called, dropping system resource usage to zero when idle.
  • Cached API version and Protobuf schema resolution: The assistant avoids making repetitive remote metadata or reflection API calls when inspecting standard fields, resources, and enums.
  • Deterministic command execution versus multi-turn LLM reasoning: Instead of the LLM guessing or iteratively debugging GAQL syntax across 3–4 round-trips, the local validator checks fields, resources, zero-impression metrics, and date clauses in a single step.

A major release built on a modern plugin architecture

This is a major release that is not compatible with prior releases. Earlier versions relied on a local workspace project structure. This version is built on a standardized plugin architecture that is installed to be globally available.

Modularizing rules, skills, and diagnostic commands into a self-contained plugin bundle allows developers to install, update, and manage the assistant across multiple environments and projects.

See the README.md for technical details on the plugin architecture.

Getting started

Because of the architectural changes in this release, review the documentation before installation:

  1. Read README_BEFORE_INSTALLATION.md for prerequisites and environment preparation.
  2. Follow the installation instructions in README.md.

We want your feedback

Share your feedback, report issues, and suggest capabilities using the survey form:

👉 Submit your feedback

Bob Hancock, Google Ads API Team