Author Archives:

Google Meet now supports sending 1080p HD video from ChromeOS meeting room hardware

We previously launched support for sending full HD video (1080p) in Meet on the web, and we’re now extending that capability to Google Meet room hardware based on ChromeOS.

Google Meet will use full HD when the additional bandwidth is needed for sharp video from the room, such as:

  • On large screens: When others in the call are viewing the room on large monitors or TVs with a layout that makes 1080p necessary, such as full-screen views in Spotlight mode, 1:1 calls or dual-screen rooms. ​
  • When someone pins your video: If a person in the meeting "pins" the room, Meet will send the highest available quality.
  • ​When the meeting is being recorded: Recorded meetings use full HD from the room for the saved meeting video.
​Full HD is available from devices that use a high-resolution camera and can handle the additional processing over a fast, stable internet connection. Meet will continue to automatically adjust video quality downwards if network constraints are detected to ensure a smooth meeting experience.

Getting started

  • Admins: There is no admin control for this feature.
  • End users: There is no end user setting for this feature; the upgrade happens seamlessly in the background when conditions are met.

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices

Resources

Google joins the Eclipse Foundation as a strategic member to accelerate AI-integrated developer tools

by amanda casari & Mike Bufano, Google Open Source

A simple image with the Google logo a plus sign and the Eclipse Foundation logo

Collaboration with the Eclipse Foundation will support open infrastructure for AI-integrated developer platforms like Google Antigravity, while advancing broader open source security and regulatory compliance initiatives

As of April 2026, Google has joined the Eclipse Foundation as a Strategic Member, reflecting the company's continued investment in open source technologies and modern developer infrastructure.

As part of this collaboration, Google will additionally sponsor Open VSX and is among the first adopters of the recently announced Open VSX Managed Registry service. Open VSX is the open source, vendor-neutral extension registry for tools built on the VS Code™ extension API. It powers a rapidly growing ecosystem of AI-integrated IDEs, cloud development environments, and developer platforms, including Google Antigravity, AWS's Kiro, Cursor, and, Windsurf among many others.

As a Strategic Member, Google will participate in the Eclipse Foundation's Board of Directors and Technical Advisory Council, helping guide the technical and strategic direction of one of the world's leading open source software foundations.

"The industry is feeling the massive turning point as AI continues to change how developers write, deploy, and maintain software," said amanda casari of Google's Open Source Programs Office and new Eclipse Board member. "Joining The Eclipse Foundation as a Strategic Member ensures that the next generation of AI-integrated developer experiences—including platforms like Google Antigravity—are built in partnership with transparent, vendor-neutral foundations. Open registries, like Open VSX, are critical infrastructure which keep the global developer ecosystem open to everyone."

Google and the Eclipse Foundation share a deep history, having collaborated across numerous initiatives since 2006. This Strategic Membership elevates the relationship and support critical to modern initiatives like Open VSX, Open Regulatory Compliance (ORC), and Adoptium.

"Google has played a pivotal role in open source innovation for two decades," said Mike Milinkovich, Executive Director of the Eclipse Foundation. "Their decision to join as a Strategic Member reflects the growing importance of open collaboration in supporting global regulatory compliance efforts, strengthening open source infrastructure, securing supply chains, and advancing the next generation of AI-integrated developer platforms."

The Eclipse Foundation continues to see explosive growth as adoption accelerates across AI-integrated developer tooling and cloud development environments. The Open VSX registry now scales to meet massive global demand:

  • 300 million+ downloads per month
  • 200 million requests during peak daily traffic
  • 12,000+ hosted extensions from over 8,000 publishers.

Introducing the Google Ads API Developer Assistant v3.0.0

We are pleased to announce the release of v3.0.0 of the Google Ads API Developer Assistant. This major release marks a significant milestone in the evolution of the Assistant, focusing on architectural modernization, improved reliability, and a more modular design.

With this release, we are migrating the Assistant to the Google Antigravity agent framework and transitioning to a Skills-based architecture. These changes make the Assistant more robust, easier to maintain, and reduce token use.

What’s new in v3.0.0?

1. Powered by the Antigravity framework

The Google Ads API Developer Assistant has migrated from gemini-cli to the Antigravity agent framework (v3.0.0). This underlying framework upgrade provides a more structured and reliable execution environment. Along with this, the directory and file structure of the project has been updated to be fully Antigravity-ready.

Support for gemini-cli will terminate on June 18, 2026, as detailed in this Google blog announcement.

2. A modular, skills-based architecture

We have transitioned the Assistant's core capabilities into Skills. Instead of relying on broad, unstructured instructions in a context file, the Assistant now loads specialized, test-backed tool directories (Skills) dynamically when needed. This drastically reduces "hallucinations" and ensures tasks are executed using precise, verified procedures.

Key updates in this modular transition include:

  • GAQL validation (validate_gaql): Moved to a dedicated skill. It now includes enhanced static query checks for date segments, click_view single-day filters, and change_status boundaries.
  • Troubleshoot conversions (troubleshoot_conversions): Replaces the old conversions_support_package. It consolidates all conversion troubleshooting and upload summary scripts, and tests into a single, cohesive skill directory.
  • Structured commands (explain and step_by_step): Converted to skills to enforce consistent, structured layouts for explanations.
  • New account mapping (get_cids_under_mcc): A new skill to retrieve all child accounts under a Manager Account (MCC).
  • New object inspection (inspect_object): A new skill for dynamically looking up Protobuf messages and Enums on the fly, to help ensure the Assistant always uses correct structures.
  • New PMax listing filter (pmax_listing_filter): A new skill to standardize listing group webpage exclusion tree modifications for Performance Max campaigns.

3. Enhanced consistency & rigor

We've introduced stricter rules and requirements to help ensure high-quality code generation and query validation:

  • Explicit API versioning: Critical skills like get_cids_under_mcc, validate_gaql, and troubleshoot_conversions now require an explicit api_version argument, eliminating ambiguity.
  • Strict GAQL rules:
    • Added a rule to AGENTS.md to prevent the use of SQL aggregate functions (such as SUM, COUNT, and AVG) in GAQL queries, as they are not supported.
    • Added a rule to check Google Ads API Developer site release notes first for the current API version to ensure the Assistant uses up-to-date documentation.
    • Streamlined configuration: AGENTS.md has been streamlined leading to a smaller initial context window. Duplicate conversion documentation has been removed in favor of programmatic skills.

4. Developer Experience (DX) improvements

We've made several quality-of-life improvements to make your development loop faster and smoother:

  • Persistent virtual environment (.venv): The virtual environment is no longer deleted at the end of a session. On startup, the Assistant checks your system's Python version; it only rebuilds the .venv if a newer Python version is available.
  • Smart API version caching: The Assistant now caches the current Google Ads API version with a TTL of 19 hours, reducing startup time by avoiding redundant network checks.
  • Better debugging with persistent logs: Log messages now include datetime stamps. The log file is written to the .agents/ directory and is no longer reset on each run, preserving history for troubleshooting.

Why should you upgrade?

The upgrade to v3.0.0 is primarily about reliability and structure. By moving to the Antigravity framework and modularizing features into Skills, we have made the Assistant more predictable and resource efficient.

If you want a faster startup, more reliable GAQL validation, and a more robust troubleshooting experience, we recommend upgrading to v3.0.0.

Get started

First installation

  1. Install Antigravity CLI: Follow instructions at https://antigravity.google/.
  2. Clone the Assistant:
git clone https://github.com/googleads/google-ads-api-developer-assistant.git
  1. Run the Install Script:
    • Linux/macOS: Run ./install.sh (defaults to Python support, use flags like --php or --ruby for other languages).
    • Windows: Open PowerShell and run .\install.ps1.

Upgrade from v2.x

  1. Copy any custom code or data from saved/ to a secure location outside the project directory.
  2. Delete your local clone of the Assistant.
  3. Clone the repository:
git clone https://github.com/googleads/google-ads-api-developer-assistant.git
  1. Run the install script (install.sh or install.ps1) to initialize the new Antigravity environment.

Bob Hancock, Google Ads API Team