Feature request: support multiple named accounts per app/connector
Open 💬 18 comments Opened Apr 30, 2026 by iamhectorlopez
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
Please support connecting multiple separately authorized accounts for the same app/connector, with explicit account selection and hard privacy boundaries.
This is different from switching the active Codex/OpenAI account or profile. One Codex session may need to work with multiple accounts for the same external service: personal Gmail and work Gmail, multiple Slack workspaces, a client Google Drive and a company Google Drive, or personal and work Google Calendars.
Today, the app/connector model appears oriented around one active connection per provider. That creates two problems:
- users have to disconnect/reconnect or switch context manually, which is slow and error-prone;
- Codex/ChatGPT can become unsafe to use for connector workflows if it is unclear which mailbox, workspace, Drive, calendar, or tenant a tool call will read from or write to.
Why this matters
This is a normal workflow for many users, not an edge case:
- Search a personal Gmail account for a receipt, then a work Gmail account for a customer thread.
- Use an internal Slack workspace and one or more client Slack workspaces.
- Compare availability across personal and work Google Calendars.
- Search a company Google Drive without also exposing personal Drive content.
- Work with more than two accounts when consulting, freelancing, or managing multiple businesses.
The current documentation reinforces the single-selected-account limitation in a few places:
- Slack is documented as one workspace at a time, requiring disconnect/reconnect to switch workspaces.
- Google app access is tied to the Google account chosen during setup.
- Google Drive setup warns users with multiple Google accounts to choose the work account and uses domain matching to prevent accidentally connecting the wrong account.
Those are useful safety controls, but the missing product capability is first-class support for multiple named connections at the same time.
Proposed behavior
Codex/ChatGPT should allow multiple named app/connector connections per provider, for example:
Gmail - PersonalGmail - WorkSlack - InternalSlack - Client AGoogle Drive - CompanyGoogle Calendar - Personal
Expected behavior:
- A user can connect more than one account/workspace for the same app/connector.
- Each connected account has a clear user-visible label, such as email address, workspace name, organization name, or user-defined nickname.
- Users can set defaults per connector, per thread, or per workspace, while still seeing which account is being used.
- When a request is ambiguous, Codex/ChatGPT asks which connected account to use before reading data or taking action.
- Prompts can target a named connection directly, e.g. "search Work Gmail" or "send this in Client A Slack".
- Tool calls expose and enforce the selected connection identity instead of silently choosing among available accounts.
- Search results, citations, and action confirmations show which account/workspace they came from.
- Users can disconnect or refresh one connected account without disturbing other accounts for the same provider.
Privacy and safety requirements
Account boundaries should be explicit and enforceable:
- Do not silently merge personal, work, and client data.
- Cross-account search, summarization, or comparison should require an explicit user instruction.
- Side-effecting actions such as sending email, posting Slack messages, editing Drive files, sharing documents, or changing calendar events should clearly confirm the selected account/workspace before execution.
- If the requested account/workspace does not match the active connector identity, fail closed instead of falling back to another account.
- Admin-managed accounts should be able to enforce domain, workspace, retention, audit, and policy restrictions.
- Memory/context should not make information from one account implicitly safe to reuse in another account context.
Related and adjacent issues
This request is related to, but narrower than, general Codex account/profile switching:
- https://github.com/openai/codex/issues/4432 - first-class multi-account auth via auth profiles
- https://github.com/openai/codex/issues/12029 - ability to use more than one Codex account
- https://github.com/openai/codex/issues/14330 - environment isolation across accounts/config/tools
It also generalizes several connector-specific problems:
- https://github.com/openai/codex/issues/19489 - Microsoft 365 connectors need explicit account and tenant selection
- https://github.com/openai/codex/issues/19669 - Slack connector stale OAuth / no reliable hot-swap path
- https://github.com/openai/codex/issues/20286 - Vercel connector cannot recover from revoked or stale OAuth grant after account switch
- https://github.com/openai/codex/pull/20265 - keys remote plugin cache by account/workspace identity, which helps with stale account state but does not appear to provide multiple simultaneous named connector accounts
Acceptance criteria
- A user can connect at least two accounts for the same provider, such as two Gmail accounts or two Slack workspaces.
- The UI clearly shows all connected accounts for a provider and which one is active for a given request.
- Ambiguous connector requests prompt for account/workspace selection before any data access.
- Connector/tool calls can target a specific named connection.
- Connector results identify the source account/workspace.
- External actions confirm the selected account/workspace before execution.
- Data from different accounts is not combined unless the user explicitly asks for cross-account work.
- Disconnecting or refreshing one account does not break other accounts for the same provider.
- Enterprise/Business admins can restrict which domains/accounts/workspaces users may connect.
18 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I work across multiple companies, each with separate Google logins. Ideally i could instantiate separate connectors for each account, then reference them explicitly, e.g. "Check Business A email for..."
I want to do this from within one codex / chatgpt account.
I'm running into this limitation as well. I regularly need to access multiple Google Workspace accounts (work, freelance, school, personal). Has anyone found a practical interim workaround or pattern for managing this more efficiently (multiple MCPs, custom plugins, or something else entirely)?
Adding a project-scoped use case that is slightly narrower than the broader multi-account request here.
I often work across multiple Codex Desktop projects/repos that map to different real-world identities. For example:
Today, the connector identity appears to be global for the provider/session. In practice this makes write-capable connectors risky: when Codex drafts or sends email, searches Drive, reads calendar events, or posts to Slack, I need to be sure the action is happening from the account that belongs to the current project context.
A useful extension of this feature would be project/workspace-level connector defaults, for example:
~/.codex/config.tomlor Desktop project settings can bind/path/to/project-atoGmail - Workand/path/to/project-btoGmail - Personal;This would reduce accidental cross-contamination between personal, company, and client data while preserving the convenience of automatic connector use.
I really need this feature as well. For me, it's Notion, but the principle is the same. I have a workspace that is integral to the way a particular project in Codex functions in terms of the automations I've set up. I have this architecture set up for multiple projects, each with their own Notion workspace.
I've just discovered that I can only have the Notion account that I've connected in Codex connected to one of those workspaces, which completely prevents me from doing what I'm trying to do. I'm really hoping the ability to create multiple instances of each connected provider comes soon.
+1. Would love to run the same automations for multiple Slack + multiple Gmail accounts. It's a bummer that I've discovered some really good workflows / automations but can only do one pair of accounts at a time
+1 to this.
I have two personal email/google accounts, and a business google workspace.
I want to make codex desktop my daily driver for everything.
It would be amazing if I can connect them all to codex with controls (e.g. slice it by project etc.)
I also very much need this feature. Who doesn't have more than one gmail account?
Yes I need this too
worked on this and a PR can be opened here: https://github.com/openai/codex/compare/main...iamhectorlopez:codex/multi-account-app-aliases?expand=1
tldr:
Codex Apps should support user-defined account aliases like Personal, Work, and University. The model can route by alias or ask when ambiguous, while the app UI can manage per-alias connections. This avoids picker spam and creates a clean path to true multi-account OAuth.
The missing production pieces are:
Example key: (app_id, account_alias) or (connector_id, account_alias).
The UI/backend needs per-alias account actions, where aliases are fully user-defined: “Connect Personal”, “Reconnect Client A”, “Disconnect University”, etc., instead of one global “Connect Gmail”.
When Codex decides “use Work”, that alias must reach the connector/tool execution layer.
The plugin page should show:
Personal -> Connected
Work -> Connect
University -> Reconnect
Tool results should probably expose or log “using Work Gmail” so the model and user do not accidentally mix accounts.
A mock app should prove two aliases can return different data.
This request maps directly to a real failure we hit today. I use a self-serve ChatGPT Business workspace for company knowledge work and Agents, but I also need a personal Pro account for higher-capacity Codex work. The same GitHub identity was connected to both workspaces. Codex code review silently billed/routed PR reviews to the exhausted Business workspace even though the Pro account had substantial usage remaining. The Pro usage dashboard and GitHub error therefore contradicted each other.
The only working recovery was to open the Business account in an Incognito window, disable auto-review, disconnect GitHub there, reconnect GitHub under Pro, and test again. There was no visible account/workspace selector explaining which entitlement would be used.
The broader business need is mixed seat tiers within one governed Business workspace: standard seats for most employees and Pro-capacity seats for a smaller group of power users. Separate personal Pro accounts fragment Agents, company knowledge, permissions, analytics, billing, and connector identity. At minimum, GitHub and other connectors should show and require an explicit account/workspace selection, including which usage pool will be charged.
+1, I would get a ton of value from this feature.
+1 - I use separate personal and work Gmail accounts, and switching the active connection is easy to get wrong. Named connections with a clear active-account indicator would be hugely useful.
+1, I'm trying to build a work around using MCP but would love this in the app.
Agreed. Come on guys! I have three different Google accounts I want to be
able to access simultaneously.
On Mon, 13 Jul 2026 at 17:38, Ahmaad @.***> wrote:
+1, I have to use alias path declared in zsh as workaround, but can only use with codex cli. Love the app so wishing this feature official support in Codex / ChatGPT app!
pls
I also have separate personal and work gmail account and google drive.