Feature request: support multiple named accounts per app/connector

## 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 worksp

Comments (0)

No comments yet. Start the discussion.

Feature request: support multiple named accounts per app/connector

Tags

Related issues

As I replied in another comment[1], it's their software, their choice.

[Feature] Support external model integration via personal API keys and local LLMs (BYOK)

> So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.