Accounts, access, and permissions
Understand the separate services, permissions, and device rules before connecting an account.
Two services, different accounts
An E2C account would identify your access to E2C's service; your Codex account provides access to a separate execution service. The connection needs to make clear which service you are signing in to and what permission you are granting. Account requirements for the free plugin have not been established and should not be assumed to match the desktop app.
Before you authorize a connection
You should be able to see where you sign in, who handles your credentials, what access you grant, and how to sign out or revoke it. E2C's connection method and the permission for that specific use and distribution still need confirmation. General documentation about an interface does not establish that every integration is permitted.
Devices and account access
The proposed E2C account policy is one person per account, with one device signed in at a time.
Its application to each product, including the free plugin, is not final. Switching devices, recovering a lost device, and restoring account access also need to be defined.
Your execution provider's account and simultaneous-use rules apply separately.
What carries between environments
Using the same provider account does not necessarily carry projects, files, workspaces, or conversation history between clients. Simultaneous access, sign-in requirements, limits, and continuity depend on the services and configuration. Automatic synchronization and uninterrupted access across clients have not been confirmed.