ChatGPT and Codex now support multiple Gmail and Google Calendar

What happened

ChatGPT and Codex Now Support Multiple Gmail and Google Calendar Accounts

OpenAI has confirmed that both ChatGPT and Codex now allow users to connect more than one Gmail account and more than one Google Calendar account at the same time. The update removes a longstanding limitation that forced users to pick a single Google identity when setting up integrations with those two services.

This piece walks through what changed, how the multi-account connection works under the hood, and what the update means for developers and everyday ChatGPT users who juggle separate personal and professional Google accounts. If you use ChatGPT or Codex alongside Google Workspace, this directly affects how you configure and use those tools going forward.

How it works

OpenAI confirmed the change publicly, with the announcement surfacing through 9to5Mac. Both ChatGPT and Codex — OpenAI's AI-powered coding environment — received the update simultaneously, signaling that the underlying connector infrastructure shared between the two products was updated rather than each receiving a separate patch. Previously, users who wanted to pull in calendar events or read email through ChatGPT were limited to a single authenticated Google account, which created friction for anyone who maintains more than one Gmail address or Google Workspace identity.

The confirmation does not include a specific rollout date beyond today, nor does it detail whether the change affects all plan tiers or only paid subscribers. Users encountering the feature for the first time will likely find it accessible through the existing integrations or connected accounts section of the ChatGPT and Codex settings panels.

When a user connects a Google account to ChatGPT or Codex, the platform uses OAuth to request access to Gmail and Google Calendar on the user's behalf. With the new multi-account support, that OAuth flow can be completed more than once, letting users authorize additional Google identities and store multiple sets of access tokens against a single ChatGPT or Codex session. Each authorized account appears as a distinct source that the model can query, letting a user ask ChatGPT to check availability across two calendars or search email from two separate inboxes within a single conversation.

Why it matters

The exact mechanism for disambiguating between accounts — whether the user must specify an account explicitly in a prompt or whether ChatGPT infers context — has not been detailed in the announcement. Builders integrating Codex into workflows that touch Gmail or Calendar should verify how account selection is surfaced in the tool's API response before building logic that assumes a single inbox or calendar stream.

The single-account restriction was a meaningful gap for anyone who uses Google Workspace professionally and maintains a personal Gmail account separately. Consultants, freelancers, and employees at organizations that permit personal device use frequently operate across two or more Google identities, and being forced to choose one made AI-assisted scheduling and email triage significantly less useful. Removing that ceiling brings ChatGPT's Google integration closer to parity with native multi-account support that Gmail and Google Calendar have offered in their own mobile and web clients for years.

Who is affected

For Codex specifically, the update matters because automated coding workflows often need to read from project-specific calendars or send notifications through work email addresses that differ from a developer's personal account. A Codex agent managing a sprint calendar while also communicating through a client-facing Gmail address now has a legitimate path to do both without requiring a workaround.

Any ChatGPT or Codex user who has connected Gmail or Google Calendar as an integration is affected by this change, since the option to add additional accounts is now present where it previously was not. The most directly impacted group is users who previously had to choose between a personal and a work Google account and settled on one at the expense of the other. That compromise is no longer necessary. Organizations that have deployed Codex for internal automation or developer tooling and have configured it against a single shared Google account may also want to revisit their setup now that separate accounts can be authorized independently.

Users who only have one Gmail address or one Google Calendar will not notice a functional difference, though the settings interface may now expose a more prominent option to add additional accounts.

What to watch next

OpenAI has not specified whether multi-account support will extend to other connected services beyond Gmail and Google Calendar. The company offers integrations with additional third-party platforms, and it is reasonable to expect similar multi-account capability to follow if the Gmail and Calendar rollout is well received. Builders using Codex in production should watch for updates to the official API documentation clarifying how account selection is exposed programmatically and whether there are limits on the total number of Google accounts that can be linked simultaneously.

On the Google side, any changes to OAuth scope requirements or token expiration policies could affect how reliably multiple accounts stay authenticated over time. Users who add a second or third account should verify that all linked accounts refresh correctly after an extended period, rather than assuming that authorization persists without reconfirmation.