ChatGPT Adds Multiple Gmail and Calendar Accounts

OpenAI DX engineer Gabriel Chua confirmed on 28 August 2026 that ChatGPT and Codex can now connect multiple Gmail, Google Calendar, and Google Contacts accounts—ending the prior one-Google-account-per-plugin limit. Users add a second or third account from the Plugins sidebar by searching Gmail, Calendar, or Contacts, opening the gear icon, and completing Google OAuth. One conversation can use a personal Gmail while another uses a work account, and ChatGPT can pull from several connected accounts when a task needs them. Availability still depends on plan, organization, and admin settings.

What exactly changed for ChatGPT and Codex Google plugins?

Until this week, each Google plugin effectively bound a single account. That forced people who keep work mail in one inbox and personal mail in another to constantly reconnect or run parallel ChatGPT sessions with awkward workarounds. Chua’s confirmation, reported by Marcus Mendes at 9to5Mac on 28 August 2026, states that multiple Gmail, Google Calendar, and Google Contacts accounts can now be added on ChatGPT and on Codex. The change is practical rather than flashy: it removes a daily friction point for anyone whose life does not fit inside one Google identity.

The flow is straightforward. Open the Plugins sidebar, search for Gmail, Calendar, or Contacts, tap the gear icon, and choose to add another account. Google’s OAuth screen appears for each new identity, so credentials stay with Google rather than being typed into ChatGPT. After authorization, the plugin list shows more than one connected account. From there, a single ChatGPT conversation can lean on personal Gmail while a second chat leans on a corporate Calendar—or ChatGPT can draw on multiple connected accounts inside one session when the prompt requires cross-inbox context.

Who can use multi-account Google plugins?

Secondary recaps say the feature is live for Plus, Pro, Business, and Enterprise users who already have access to the relevant plugins. Free-tier claims are not established in the 9to5Mac report, so treat multi-account Google plugins as a paid or plugin-enabled capability unless OpenAI publishes otherwise. Workspace admins can still restrict which connectors are allowed, which identities may be linked, and whether Codex inherits the same Google scopes as ChatGPT. OpenAI’s plugins documentation remains the authority for org-level toggles; Chua’s note confirms product capability, not a universal entitlement.

That admin surface matters for regulated teams. A company that previously blocked Gmail plugins because employees might mix personal and work data now faces a more nuanced choice: allow multi-account linking with clear policy, or keep the connector off. Individuals on Plus or Pro who juggle freelancing and day jobs gain the most immediate productivity win. Related PromptCrates coverage of <a href="https://www.promptcrates.com/news/chatgpt-save-temporary-chats-personalization-controls">ChatGPT temporary chats and personalization controls</a> and <a href="https://www.promptcrates.com/news/chatgpt-work-secure-website-sign-in">ChatGPT work secure website sign-in</a> shows how OpenAI has been stacking identity and privacy toggles around the same assistant.

How does this compare with other assistant email plugins?

Anthropic’s Claude already offers Gmail send capabilities on paid Cowork plans, documented in <a href="https://www.promptcrates.com/news/anthropic-claude-gmail-send-cowork-paid-plans">Claude Gmail send on Cowork paid plans</a>. OpenAI’s move is less about sending and more about parallel identity: keeping personal and work Google graphs attached without constant re-auth. ChatGPT’s broader plugin surface—see also <a href="https://www.promptcrates.com/news/chatgpt-apple-messages-plugin-send-texts">the Apple Messages plugin for sending texts</a>—makes multi-account Google support a consistency play. Once users expect one assistant to talk to Messages, Calendar, and mail, forcing a single Google login becomes an obvious gap competitors can exploit.

Codex receiving the same multi-account treatment is notable for developers. Coding agents that file issues, read calendar blocks before merging, or draft emails from a work alias need the corporate Google identity; personal Gmail remains useful for side projects. Aligning ChatGPT chat and Codex tooling on multi-account OAuth reduces context-switching bugs where an agent silently uses the wrong inbox. Teams should still audit OAuth scopes after linking a second account and revoke unused Google apps from their Google Account security page.

What should users do to set this up safely?

Start with the lowest-privilege Google account you actually need for a given workflow, then add a second only when a prompt fails without it. Label chats clearly—“work calendar” versus “personal triage”—so you do not ask the model to summarize a confidential thread while the personal account is also in scope. On Business and Enterprise, confirm with your admin that multi-account linking is permitted and that logging captures which Google identity was queried. If your organization forbids personal accounts on corporate devices, keep personal Gmail off ChatGPT at work even though the product now allows it.

Gabriel Chua’s 28 August confirmation closes a long-standing plugin limitation. ChatGPT and Codex can attach multiple Gmail, Calendar, and Contacts accounts through gear-icon OAuth; conversations can stick to one identity or pull across several when needed; and plan plus admin settings still gate who gets the feature. For day-to-day users on Plus, Pro, Business, or Enterprise with plugins enabled, the practical upgrade is simple: stop reconnecting Google every time your work and life inboxes diverge.

Sources

• <a href="https://9to5mac.com/2026/08/28/chatgpt-and-codex-now-support-multiple-gmail-and-google-calendar-accounts/">ChatGPT and Codex now support multiple Gmail and Google Calendar accounts</a> — 9to5Mac (Marcus Mendes), 28 August 2026