Connect computers and apps to your dot | ChatGPT Learn

Open original

This is ChatGPT's help doc on giving your "dot" (a cloud-based assistant) its own cloud computer, access to your local machine, and permission to use your apps and websites. It covers how to connect, what access each step grants, and how logins and sessions are handled.

  • The dot runs on its own cloud computer with separate files, software, and browser sessions, so it keeps working when your own machine is off, and signing in on your computer doesn't sign the dot in anywhere.
  • Connecting a local computer is a separate permission from Codex or Work Sync, and it persists until you revoke it. An Offline status pauses access but doesn't remove it.
  • Website logins go through a private form sent to the remote browser outside the chat, and saved logins are optional and need your confirmation to reuse. Saved logins and active sessions are treated as different things.
  • App access is scoped per plugin and per permission, so you can let the dot read Gmail without letting it send email. Messaging the dot through a channel like Slack doesn't connect your inbox.

Your dot runs in the cloud with its own computer and browser, so it keeps working when your laptop is off. The cloud machine has its own files, software, and browser sessions, and it doesn't inherit anything from your personal browser. That last point matters in practice: signing into a site on your own machine doesn't sign the dot in. Under your dot's profile, the Computers section lets you inspect that cloud machine, and when the dot offers a browser handoff, Open computer brings you into it. Opening the computer doesn't hand over control, though. You have to select Take over to get the mouse and keyboard, and Return control when you're done so the dot can resume. Cloud threads can run in parallel, so you can keep chatting while several tasks grind away, and for coding, the dot can use a Codex cloud environment you've configured with the right repository. Logins are where the details get fiddly. When a site needs credentials, the dot sends a private form. You type your password and any verification code there, and that information goes to the remote browser without passing through the conversation. Alternatively, you can sign in yourself through takeover mode. A website session stays alive until you sign out or the site expires it, but some sites block cloud browsers or demand extra verification. Save to Passwords is optional. If you save a login, a later request can offer it, but the dot will only reuse it after you confirm. Keeping a saved login separate from an active session is worth remembering: the dot can keep using a live session without asking again, but a saved credential always needs your okay. Connecting your own computer is a separate step, and it's the one that gives the dot access to local files, code, and apps. You allow it once per machine from the profile in the ChatGPT app, and the connection persists as long as the computer stays online and the app stays open. An Offline status doesn't revoke anything, but Revoke access does. Each computer can run one thread at a time, so independent jobs go on separate threads per machine. If a site blocks the cloud browser, you can ask the dot to try your local machine, which spins up a separate local task rather than transferring the cloud session. App connections work similarly: install and connect plugins like Gmail, Google Drive, or GitHub, then limit what each one can do. You can allow reading email without allowing sending it. Messaging the dot from Slack, for instance, grants no access to your inbox, and neither the computer link nor the Codex or Work Sync connections give the dot access on their own.

Ask about this article