On October 15, 2026, I reproduced an account-binding failure in ChatGPT Work on iOS with two Gmail accounts connected.
What the interface displayed
Immediately above the executable email card, ChatGPT identified the sender as the Deborah account, the destination as OpenAI Support, and the status as “Draft — not sent.”
What the executable card was actually bound to
The card’s sender field showed the other connected Gmail account—the Angelina account—while its recipient, subject, and body concerned the Deborah account and Deborah’s support case.
The conversational confirmation and the executable connector binding therefore disagreed inside the same response. Had the card been sent, the message would have come from the wrong account identity and contaminated an unrelated support record.
This is not a request to add multiple-account functionality. OpenAI’s own ChatGPT Work guidance tells customers with multiple accounts to review each separately and to check that the correct accounts are selected. OpenAI Support also stated in the forum that some apps now support multiple accounts through “Connected accounts → Connect another.” The supported selection must remain stable through execution.
Required correction
- Carry one immutable connection/account identifier from selection through rendering, approval, execution, and audit.
- Display the actual connector-bound sender inside the action card before Send is enabled.
- Fail closed whenever the conversational sender label and executable connector binding disagree.
- Never silently substitute the default, first-connected, or most recently used account.
- Record the exact sending account and resulting message identifier in the completion record.
- Allow a chat, project, or scheduled task to be explicitly bound to one named connection.
Platform: ChatGPT iOS 1.2026.272 (build 37078235773); iOS 26.6.2; iPhone 16 Pro Max. Reproduced October 15, 2026 at approximately 12:15 PM Pacific. A screenshot was preserved and supplied directly to OpenAI Support.
Related discussions: