Is one Dot enough, or does a second job need a second Dot so they do not share files?

One Dot is what you have, and a second job on that Dot does share its cloud files. OpenAI’s getting-started page says your first Dot is included with ChatGPT Pro or Business Premium, and that adding more Dots is in the future, along with a way to scale a Dot’s speed or monthly work. The announcement says each Dot works on its own cloud computer, and that today you start with a primary Dot. You cannot yet open a second Dot to wall off a second job. Until that exists, both jobs live on the one computer, with its files, software, and browser sessions.

That is the opposite of hoping a nickname creates a disk. A Dot announced on 29 September 2026, on GPT-6 Astra, has one cloud computer for the jobs you give that Dot. Your own computer stays separate unless you connect it, and you can connect only one personal computer at a time. Specialist Dots for companies are described as a preview, with their own identity for access management, not as a button that splits your personal files this week.

What does the one computer actually hold?

Its own files, its own software, and its own browser sessions. The computers guide says cloud work can continue while your devices are off, and that the computer keeps state between periods of use. Signing in on your laptop does not sign the Dot in. A session on the Dot’s browser remains until you sign out or the site expires it. Every task you hand the same Dot can see that state. A research job and a finance job are not two browsers because you used two chats. Cloud threads let the Dot work on several things in parallel, and you can keep talking while they run. Parallel threads are still one computer. A file saved for the first thread is on the disk the second thread uses.

Plugins are account-scoped in a way the disk is not waiting on a second Dot to fix. Permissions you set for a ChatGPT app apply to the Dot, and the privacy FAQ says those plugin permissions apply across Dots, ChatGPT, ChatGPT Work, and Codex. A read-only mail connection is read-only for the Dot you have. It is not a per-job vault. If you connect a drive or a repository, every task on that Dot that is allowed to use the plugin can use it within those permissions. Disconnecting the app does not delete information the Dot already obtained. Deleting that means deleting the Dot.

Why a second Dot is the wrong tool this month

Because OpenAI has not handed you one. The sentence in both the announcement and the help article is “in the future, you’ll be able to add more dots.” The same announcement says they envision teams of Dots over time, and that a preview of specialist Dots is being shared for organizations, with identity aimed at access management and company systems. I am not going to describe a create-second-Dot control I did not find on the getting-started page. If your account only shows the primary Dot, that is the product as documented in October 2026, not a setup mistake.

When more Dots do exist, the line OpenAI already wrote is that each works on its own cloud computer, and your computer’s contents stay separate unless you connect them. That is a different design from Grok Bots, which share one cloud computer and its logins. Do not import that habit. Do not assume, either, that a future second Dot will refuse an app you connected at the account level. Plugin permissions are already described as shared across Dots. A second computer would separate files and browser sessions that live on the Dot. It would not automatically separate a Gmail plugin you enabled for the account. I have not seen a help page that spells out per-Dot plugin isolation for a product that still says additional Dots are future. Treat account connections as shared until a page says otherwise.

How do you keep two jobs from using the same secrets on one Dot?

Do not put the second job’s secrets on that computer. The cloud browser session is the Dot’s. If job A needed a bank login and job B is a writing project, do not sign the bank in “just in case,” and sign out when the bank task is done. Save to Passwords is optional. Reusing a saved login requires your confirmation, and a custom rule cannot remove that confirmation. Confirmation is not a wall between jobs. It is a tap. If both jobs are ones you are willing to confirm for, the saved login is available to the Dot, not to a folder.

Keep the sensitive work off the Dot’s disk when the two jobs do not share a trust level. Your computer is the other machine, and it starts disconnected. Allow access is explicit, one computer, and the ChatGPT app has to stay open while the Dot uses it. Revoke access removes that path. It does not wipe the cloud computer. A local task and a cloud task can run with the cloud half managing and the local half touching your files. Open the task and see where it is happening before you assume a file stayed in the cloud. If the second job must not see your laptop, do not turn Allow access on for a Dot that also does the first job.

Use the instruction scope as a habit, not as a security boundary. “Draft the newsletter from this folder” is a scope. It does not encrypt the other folder. The Dot can still open files on its computer if a later instruction, or a mistake, asks it to. OpenAI says custom rules are instructions it tries to follow and that it can make mistakes, and that rules do not grant or, by themselves, remove app access. A rule that says “never open the finance folder” is a wish you should still test. The reliable version is that the finance files are not on that computer.

What about the company preview?

Specialist Dots, in the announcement, are a preview for organizations: their own identity, access management, and deeper ties to company systems of record. That is the direction of “a second job gets a second actor.” It is not documented as a personal Pro feature you enable beside the primary Dot. Enterprise Dots are still off until a workspace owner enables Use dots (Beta). Even then, the help page I read talks about a member’s Dot and a member’s cloud computer, not about a self-serve pair of Dots with two disks. Workspace cloud browser, network, and computer-use settings apply to Dots. They do not split one member’s Dot into two file systems.

Reset deletes the Dot you have: conversations, saved memories, and scheduled tasks. It does not spawn a fresh second Dot that inherits nothing while the first one remains. Read the notice. Deleting does not undo changes already made in connected apps or recall messages already sent. If the two jobs have already mixed files on the cloud computer, reset is a burn-down of the Dot, not a sort.

What does “scale the Dot” mean, if not a second disk?

The help article pairs “add more dots” with a different future lever: scale the output of each Dot by increasing its speed or the amount of work it can take on per month. That is capacity, not isolation. A faster primary Dot is still one computer. An allowance for deeper work, with extended limits in the first month, is also about how much it can do, not about splitting files. I have not found a price for a second Dot, and I am not going to invent one. If a settings screen later offers another Dot, read whether it has its own computer before you put a secret on it. Until that screen exists, scaling the one you have will not unshare the disk.

Folders on that disk are hygiene. They help you find the newsletter and the notes. They are not an access control the computers page describes. The page describes one computer with its own files. Ask the Dot to keep a project in a named directory if you want the work findable. Do not tell yourself the other project cannot open it. If you need that guarantee, the file does not belong there.

So which way do you go this week?

Use one Dot for jobs that are allowed to see the same files and the same browser. Keep a job that must not see them off that Dot: different apps disconnected, no saved login, no Allow access on the laptop, or do the sensitive half yourself. Do not wait on a second Dot to create a wall the product has scheduled for later. When OpenAI does let you add one, read whether that Dot gets its own computer, which the announcement already promises as the shape, and whether your plugins follow it, which today’s permission notes suggest they might. Until both of those are true in your account, one Dot is enough only when one trust level is enough. A second job that needs a second disk needs a place that is not this Dot’s computer, not a second name on the same one.