OpenAI’s current computer-and-apps guide says a dot has its own cloud browser sessions. Signing in on a personal computer does not sign the cloud browser in. A website session can remain available for later work until the user signs out or the website expires it, but some sites block cloud browsers or require additional verification. The guide provides no universal lifetime for those sessions.
The same documentation distinguishes an active session from an optionally saved login. A dot can use a valid session without another sign-in; reusing a saved login for a new sign-in requires confirmation. The documented private sign-in form keeps credential entry outside the conversation, and browser takeover is another supported route. These are documented behaviors, not a new release or a guarantee for every website.
Editorial take: Plan recurring browser work with a recovery step. Specify where the result belongs and what should happen if authentication expires. A missed run should produce a clear access blocker, not an assumption that the account is permanently connected or a request to paste a password into chat.