ChatGPT code reveals dots are getting their own permanent email addresses

Verified 2026-10-10

#What happened

Original reporting by RuntimeWire (Ryan Merket, published Oct 7, 2026), based on reverse engineering of the official ChatGPT Windows app: the bundled client code contains a native email-address setup flow for ChatGPT dots that is still under development. It covers personal-handle claims, separate work-address logic, claim and link requests that record consent version 1, and controls for activating, disconnecting, and reconnecting an address.

#Why it matters

The code indicates dots could get their own email addresses: personal handles described in one dialog as permanent and not editable, plus fixed work addresses that users cannot customize. RuntimeWire did not confirm the feature is available to ordinary accounts, and OpenAI's rollout plans, retention rules, sending limits, and qualifying plans remain unconfirmed.

#Personal handles

For a personal address, the client accepts a handle of one to 30 lowercase letters, digits, hyphens or dots (dots cannot appear at the beginning or end, or consecutively). The code says no suffix is added to a personal handle; the domain comes from the server. One standalone dialog warns: "This email is permanent and cannot be edited." The same component has a setup presentation that does not render the warning in the inspected branch, so the permanence rule exists in code but its presentation in a released interface is still open.

#Work accounts

Work-account handling follows a separate path: the component recognizes workspace subdomains under chatgpt.email (with staging and testing variants) and supports a server flag for automatic work-address allocation. It can use a suggested address or an existing claim. A fallback derives the local part from the employee's login alias and appends "-dot." The interface presents work addresses as fixed and tells users they cannot customize them.

#Consent and permissions

Claiming and sending activation are connected in the client: claim and link requests record consent version 1, and an already-linked address without the expected consent can show an "Enable email sending" action. The interface describes activation as operating under the dot's normal permissions; the code does not establish unrestricted outbound mail, recipient rules, sending limits, or delivery reliability. Setup requires an active cloud dot, and the client handles error states for workspace-admin blocks, ineligible accounts, unavailable addresses, quotas, and missing sending permission.

#What is not confirmed

RuntimeWire did not confirm the flow is available to ordinary accounts, did not claim an address, and did not send a message. Its images are labeled reconstructions, not screenshots of an activated feature. OpenAI's intended rollout, retention policy after account deletion, ownership-transfer rules, sending limits, and which plans qualify remain unconfirmed, and OpenAI was not contacted before publication. OpenAI's getting-started guide, checked on October 7, says users can connect a personal email account while standalone addresses for dots are unavailable at launch; a separate privacy FAQ refers to a dot having its own email or Slack account.

#Sources

• RuntimeWire: https://runtimewire.com/article/chatgpt-code-reveals-permanent-email-addresses-for-dots-and-fixed-work-account-h-1