The change was reported on August 28, 2026, based on confirmation attributed to an OpenAI DX engineer. It describes support for adding a second or third Google account to the relevant connections in ChatGPT and Codex. OpenAI’s own account-management guidance independently confirms the broader mechanism: some apps can support multiple connected accounts, users may see a Connect another account option, and account selection can be specified in a request when the app supports it.
That distinction matters. Multi-account connections are an important usability improvement, particularly on a Windows PC used for both personal and managed-work tasks. But the available official documentation says support is conditional on the app and the user’s account; it does not explicitly spell out the Google-app rollout, a maximum number of accounts, or exact rules for cross-account search and calendar aggregation.
What is reportedly changing
The reported update applies to the Gmail, Google Calendar, and Google Contacts connections in ChatGPT and Codex. Rather than replacing an existing Google authorization, a user can reportedly retain it and add another Google account through the connection’s settings.
The reported workflow is straightforward:
- Open the Plugins area in ChatGPT or Codex.
- Find the existing Gmail, Google Calendar, or Google Contacts connection.
- Open its gear or settings control.
- Choose the option to add another account, where available.
- Sign in to and authorize the additional Google account.
This aligns with OpenAI’s general documentation for apps that offer multi-account support. However, availability is not universal. Whether an app exposes the additional-account option can depend on the app itself and on the particular ChatGPT account.
The practical benefit is persistence. Previously, the relevant Google connection was widely understood to operate around one active account at a time. Users who needed to alternate between identities could face a disconnect-and-reconnect routine or otherwise change context before asking ChatGPT or Codex to work with the intended mailbox or calendar. An OpenAI Academy session in June reflected that earlier understanding, although the employee speaking there explicitly qualified it as tentative. User requests in August, and an earlier Codex feature request, also described the pain of keeping personal and professional accounts separate.
Adding accounts is not the same as merging them. That is a useful limitation as well as a usability caveat: distinct Google identities can remain separately authorized rather than forcing users to funnel several accounts through one shared credential context.
Do not assume it searches every inbox at once
The most consequential unanswered question is how ChatGPT chooses among connected accounts during a real request.
A user might reasonably expect a prompt such as “Find the latest invoice in my email” to search every linked Gmail account. Or they might expect “What meetings do I have tomorrow?” to combine calendars from personal and work identities. The available evidence does not establish either behavior.
OpenAI’s official account guidance instead says that, when supported, a user can specify the intended account in a request. That points toward a safer operating habit on Windows, especially for people with accounts serving different roles: state the account clearly.
Examples of more precise requests include:
- “Using my work Google account, summarize unread messages from the finance team.”
- “Check my personal calendar for appointments this Friday.”
- “Search the archive account for messages containing the project name.”
Until the product behavior is fully documented, users should not rely on implicit cross-account searching, automatic calendar consolidation, or reliable selection based merely on conversation context. If a response has business, legal, scheduling, or privacy consequences, verify which connected account was used and cross-check the result in Gmail or Google Calendar.
The distinction is especially important for similarly named contacts, overlapping events, and email threads that exist in more than one account. A polished AI response can still be incomplete if it looked in the wrong place—or only one of several places.
Why the improvement matters for PC workflows
Multi-account support is most useful where one Windows device is the hub for several identities. A freelancer might have a personal Gmail account, a client-managed Google Workspace account, and an archive mailbox. A student employee may have school and work calendars alongside a private account. A small-business owner may need to keep a customer-facing address distinct from an administrative one.
In such cases, account switching is not only inconvenient. It increases the chance that a user will ask a question while the wrong identity is active, miss an event in another calendar, or avoid using the connection altogether because reauthorization takes too long.
For Codex users, the same issue can be sharper. Developer and IT work often involves separate organizational boundaries, different repositories, and different collaboration systems. The reported change covers Google apps, not every provider or every connected service. Still, retaining several Google authorizations could reduce one source of friction for people using Codex alongside multiple work contexts.
It is also worth keeping the historical scale in perspective. Gmail, Google Calendar, and Google Contacts connections first began rolling out to ChatGPT Pro users in August 2025. Plus access followed globally the next day, while Team, Enterprise, and Edu availability was described as following later. The new reported development is not the arrival of Google connections themselves; it is the ability to attach multiple Google accounts to these particular connections.
Enterprise controls still decide what is possible
A second Google account appearing in the connection flow does not override workplace policy. In an organization using Google Workspace, there are at least two separate control layers to consider.
First, the Google side can limit OAuth approvals and the scopes an external app may receive. A Workspace administrator may block the connection, restrict authorization, or limit which domains can be used. That means an employee may be able to link a personal Google account while finding that their company account is unavailable or subject to a separate approval process.
Second, ChatGPT workspace administration can control app access and actions. OpenAI’s documentation says availability can vary by plan, region, workspace, role, model, and interface. Workspace administrators can also restrict connected accounts to approved domains.
For a managed Windows fleet, this means the feature should be treated as a governance question rather than merely an end-user convenience setting. IT and security teams should establish whether staff may connect personal accounts, whether only corporate domains are allowed, which data categories can be read, and which actions—if any—are permitted through connected apps.
Users should not interpret successful sign-in as blanket authorization to expose company information in an AI conversation. The Google authorization governs what the connection can access; organizational policies and the content of prompts still determine whether using that access is appropriate.
Privacy: account access is bounded, but retention deserves attention
OpenAI says that a ChatGPT connection to an individual Google account can access only content available to the account that the user authorized. In plain terms, linking a personal Gmail account does not by itself grant access to a separate employer-owned inbox. Each identity requires its own authorization, subject to Google and workspace controls.
That is an important boundary, but it is not the whole privacy story. OpenAI states that connected Google-app data is not used directly to train generalized models except in specified circumstances, including when a user submits feedback or when information is copied into a conversation or included in a response.
Users should be careful with the latter exception. Even if a connected-app lookup has a constrained data policy, pasted emails, quoted calendar details, and material returned into a chat can change the handling context. Before asking for summaries of contracts, personnel discussions, customer correspondence, medical appointments, or confidential project calendars, users should understand their employer’s policy and the controls attached to their ChatGPT workspace.
Memory is another separate setting. Eligible information from Google apps may be used by ChatGPT Memory if Memory is enabled. Disconnecting an app does not automatically delete existing conversations or saved memories. Therefore, disconnecting an old work account after changing jobs is prudent, but it should not be the final step. Review relevant conversations and Memory settings as well.
The broader account-management problem remains open
The reported Google change addresses a real part of the multi-account problem, but the larger request from advanced users is more demanding.
A Codex feature request filed in April called for multiple separately authorized accounts across providers, named account controls, explicit selection, account-specific results, and confirmation before actions that have side effects. It also sought hard boundaries so information from one identity is not silently mixed with another.
The reported update should not be presented as proof that all of those capabilities now exist. The available information concerns Gmail, Google Calendar, and Google Contacts, with a reported path for adding further Google accounts. It does not verify named labels, project-level defaults, result provenance, default search behavior, non-merging safeguards, or confirmation flows for actions. Nor does it establish comparable support for services such as Slack, Google Drive, or other providers.
This is more than a feature-list technicality. Good multi-account design needs users to know exactly which identity supplied an answer and which identity will be affected before an action is taken. Those safeguards become essential when work and personal information coexist in the same AI interface.
How to use it safely on Windows
If multi-account options appear for your Google connections, start with a conservative setup:
- Connect only accounts you genuinely need in ChatGPT or Codex.
- Read the Google authorization screen before approving access.
- Use clear account-specific wording in prompts rather than assuming automatic aggregation.
- Verify high-stakes email, contacts, and calendar answers in the original Google app.
- Avoid placing sensitive material into chat prompts unless your organization permits it.
- Review ChatGPT Memory if you use connected Google services and Memory is enabled.
- When an account is no longer needed, disconnect it and separately review related chats and saved memories.
- In a workplace, ask the administrator or security team whether the relevant Google domain and ChatGPT app connection are approved.
For ordinary users, the update may make ChatGPT more practical as a helper across separate life and work identities. For administrators, it reinforces the need to manage AI connections with the same care applied to browser extensions, OAuth consent, and cloud collaboration tools.
The immediate takeaway is modest but meaningful: ChatGPT and Codex reportedly have a path to retain multiple Google accounts for Gmail, Calendar, and Contacts. Treat that as an improvement in connection management—not yet as evidence that the products will intelligently, safely, and transparently unify every account in a single prompt.
