Gemini conversation history is coming to the side panel in Google Workspace

Conversation history is coming to the Gemini side panel in Google Workspace apps. This feature will enable users to resume their conversations with Gemini across sessions. This history will only persist in a single app and conversations will remain private. For example, a conversation in the side panel of Google Docs will not appear in the side panel of Google Sheets, and a conversation in the side panel of a shared file will not be visible to other users with access to that file.

Timeline
  • As of February 25, 2026: Admin controls for conversation history are available. See below for more details and recommended actions.
  • Starting March 3, 2026: Conversation history will start rolling out to end users participating in the Gemini Alpha and Workspace Labs programs.
  • No sooner than March 17, 2026: Conversation history will begin rolling out to all other Workspace users. We’ll provide an update on this blog before that rollout begins.
Accessing conversation history in the side panel of Google Drive
Deletion controls
This launch includes two new controls for administrators to ensure conversation data management aligns with organizational policies: the ability to decide if users can manually delete their history and the ability to set automated retention periods to manage the data lifecycle effectively. These settings can be configured at the domain, organizational unit, or group level.

This launch does not include Vault support or the ability for end users to auto-delete conversations; we’ll roll these features out in the future. Stay tuned to the Workspace Updates blog for more details when these features launch.

Getting started

  • Admins: Visit the Help Center to learn how to manage Gemini in Workspace conversation history for your organization using the settings below.
    • Manual deletion: This setting is ON by default, meaning end users can manually delete individual conversations unless the setting is changed.
    • Auto-deletion: Conversations are stored indefinitely by default, unless admins enable auto-deletion. If enabled, admins can choose to delete inactive chats after three months, 18 months, or three years.
  • End users: Once the feature is live, users can access their history within the Gemini side panel of the specific app they are using.
    • History will only begin to populate once the feature is live for a specific user; conversations held prior to the rollout will not be saved.
    • Users must have smart features and personalization turned on to access Gemini in Workspace services.
    • Conversations remain private; users can only view their own individual history.
    • Depending on the admin settings above, users may be able to manually delete individual conversations.

Rollout pace

Availability

  • Business: Business Starter, Standard, and Plus
  • Enterprise: Enterprise Starter, Standard, and Plus
  • Other Editions: Frontline Plus
  • Education: Education Plus
  • Other Add-ons: Teaching & Learning
  • AI Add-ons: Google AI Pro for Education
  • Consumer: Google AI Pro and Ultra
Note: Gemini in Workspace is currently available to users over the age of 18 with eligible Google Workspace plans.

Resources

Chrome Dev for Desktop Update

The Dev channel has been updated to 147.0.7703.0 for Windows, Mac and Linux.

A partial list of changes is available in the Git log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Chrome Release Team
Google Chrome

Introducing Google Ads API Developer Assistant v2.0

This major update transforms the Assistant from a powerful code generation tool into a proactive troubleshooting and automation partner for Google Ads developers. Since our v1.6.0 release, we've listened to your feedback and focused on the most challenging parts of API development: diagnostics, consistency, and setup.

What’s new in v2.0?

1. Simpler Installation & Maintenance

Setting up a multi-language development environment shouldn't be a chore.

  • One-Command Setup: Use the new --install-deps flag with install.sh or install.ps1 to handle pip, composer, and bundler dependencies in one go.
  • Unified Directory Structure: All your generated code, CSV exports, and diagnostic reports are now organized under a single saved/ directory with sub-directories for each type of output.
  • One-Command Update: When a new version of the API and the client libraries are released you need to execute update.sh to work with the latest version. You can also use update.sh to add additional client libraries to your context.

2. Agentic conversion troubleshooting

Offline conversion tracking is one of the most powerful—yet complex—features of the Google Ads API. Debugging why a conversion wasn't attributed can be a time-consuming manual process.

In v2.0, we’ve introduced a dedicated Conversion Troubleshooting & Diagnostics suite.

  • New Script: api_examples/collect_conversions_troubleshooting_data.py
  • New Command: /conversions_support_data

The script executes standard reports for conversions troubleshooting and provides context for the Assistant to troubleshoot your issues.

The command is most useful after the Assistant has analyzed your conversion problem and attempted to solve it. If it cannot, and you need to contact support, this command will analyze your customer settings, conversion actions, and upload summaries to generate a structured diagnostic report based on the analysis already performed. It even identifies "unhealthy" states and high failure rates automatically, saving you hours of log diving. It saves the results to a text file that you can include with a support request should you need to file one.

3. Built for the latest API (v23)

Version 2.0 fully supports Google Ads API v23. All our interactive examples have been updated, and the Assistant's internal context is now optimized for the latest resources and fields, ensuring the code you generate is production-ready.

4. Seamless Automation with Session Hooks

We’ve added SessionStart and SessionEnd hooks to make your workflow truly frictionless.

  • Automatic Configuration: The Assistant can now automatically locate your configuration file in your $HOME directory at the start of a session. It copies it to the sub-directory config in your project directory. Python is Gemini’s preferred language to query the API. So, if you are using another language, it reads your configuration file and creates a temporary google-ads.yaml in config for its queries, but continues to respond in the code of your preferred language.
  • Auto-Cleanup: Temporary configurations are securely wiped when you exit, keeping your workspace clean and your credentials safe.

5. Smarter GAQL validation

Building complex GAQL queries is easier than ever. We've updated GEMINI.md and conversions/GEMINI.md with rigorous validation rules for the latest API edge cases, including improved handling of date segments and finite range requirements. The Assistant now catches logic errors before you execute the query.

6. Skills

Think of a Skill as a mini-plugin or a "behavior blueprint." While the general context (like your GEMINI.md file) provides background info, a Skill is only "loaded" into the AI's brain when it specifically needs to perform a complex, procedural task like obtaining the current version of this extension. You don’t execute the Skill directly. Gemini decides when it needs it.

Although still an experimental feature, we have included one with this release to compliment our use of hooks for session initialization and cleanup.

Why Should You Upgrade?

The leap from v1.6.0 to v2.0.0 is about more than just new features; it’s about reliability. By integrating deep API knowledge with automated diagnostic tools, v2.0 reduces the "trial and error" loop that often slows down API integration.

Whether you're debugging conversion uploads or building complex reporting pipelines, v2.0 gives you the tools to work faster and with more confidence.

Getting Started

First installation

Upgrading from a previous version

  • Copy any custom code from saved_code/ and saved_csv/ to a secure location.
  • Delete your local clone of the Google Ads API Developer Assistant by deleting your project directory and all sub-directories and files.
  • git clone https://github.com/googleads/google-ads-api-developer-assistant.git
  • In the project directory, run install.sh or install.ps1 to install the extension and client libraries.

Bob Hancock, Google Ads API Team

Additional changes for supporting European Union Political Ads Regulation in Google Ads API and Google Ads scripts

What’s changing?

In 2025, Google rolled out changes to support the EU Political Ads Regulation in the Google Ads API and Google Ads scripts. On April 1, 2026, we will change account-level API restrictions. If you use either of these products to create or manage campaigns, you may need to update your application before April 1, 2026 to handle these enforcements.

API validation and enforcement changes

On April 1, 2026, Google Ads API and Google Ads scripts will implement the following changes in versions v20, v21, v22 and v23 of the API.

    select campaign.id
      from
        campaign
      where 
        campaign.missing_eu_political_advertising_declaration = true

How will this affect my campaign serving?

Any campaign that has declared EU political ads by setting contains_eu_political_advertising to true will stop serving ads in the EU. Refer to the Help Center to learn more.

What do I need to do?

If your application uses either the Google Ads API or Google Ads scripts to create or manage campaigns, make sure to update your application to handle these enforcements before April 1, 2026.

How do I get help?

Reach out to the Google Ads API support or Google Ads scripts support channels if you have more questions about this change.