# ChatGPT Dots: What OpenAI's Always-On Agents Mean for How I Work as a Lead SWE > Source: > Published: 2026-09-30 04:04:38+00:00 Have you ever closed your laptop at night knowing that three things will quietly rot while you sleep? A flaky test nobody owns. A customer complaint that will sit in a Slack thread until someone has "a minute". A proposal doc that is already out of date because the requirements changed at 6 PM. As a Lead Software Engineer, most of my job isn't writing code. It's keeping a dozen half-finished threads from falling on the floor. So when OpenAI published "Introducing dots" on September 29, 2026, I didn't skim it. I read it the way I read an RFC: slowly, looking for the parts that are concrete and the parts that are just vibes. This post is my breakdown. Everything here about the product comes straight from OpenAI's announcement. Where I'm speculating or giving my own opinion, I'll say so clearly. In OpenAI's words, dots are "remarkably capable, always-on agents" that live in ChatGPT. The pitch is simple: an assistant that gets to know what matters to you, keeps working on your behalf, and takes work off your plate so you get your time and attention back. The concrete details are what caught my eye as an engineer: You start with a single **primary dot**. You give it a name and make it your own. OpenAI says that over time they envision *teams* of dots working together for you, but today the starting point is one dot per person. That's the part that matters to me. This isn't a chat window that forgets you when you close the tab. It's a persistent worker with its own machine. The mental model shift here is bigger than it looks. With a normal chat assistant, I'm the scheduler. I decide when it runs, I paste in context, and I babysit every step. OpenAI describes dots differently. Your dot can take a project and run with it, even while it's working on several others. You can keep handing it new tasks and ideas without juggling separate threads or directing every step. The more you work together, the more it learns your preferences, how you think, and, in OpenAI's phrase, "what good looks like to you." There's also a proactive side. OpenAI says the magic is when a dot brings you work done the way you would do it, "sometimes before you even think to ask." They share a few internal examples: My favourite example is the least flashy one. An early tester's dot noticed he had forgotten to invoice a publication. It prepared the invoice and sent it **after his approval**. That last bit matters, and I'll come back to it. Here's what the announcement says about mechanics. No speculation. **Its own computer.** Dots can do nearly anything using their own cloud computer, their own browser, and the apps you've connected. You can open your dot's computer at any time to inspect its work. As someone who has debugged plenty of "the agent said it did it" situations, being able to look at the actual machine is the feature I care about most. **Your devices, if you allow it.** Dots can connect to other devices besides their own. You can also give your dot permission to connect to and use your laptop, so it can work directly alongside you. That's opt-in. Your computer stays separate unless you choose to connect it. **Proactive research.** When you aren't actively working with it, your dot looks for ways to help in the background. OpenAI calls this "proactive research." The important constraint is that this runs on the apps you've already connected, using tools that are **restricted to be read-only**. In background mode it can't send messages, change app content, or control your browser or computer. **Where you talk to it.** You can message *or call* your dot in ChatGPT on desktop, web, and mobile. You can also message it in **Slack and Teams**, and OpenAI says texting is coming soon. Dots carry context across every channel. So I could start something in ChatGPT, drop context in a team Slack channel, and the dot follows through with the full picture. It can also message *you* with progress, questions, or decisions that need you. OpenAI lists several "extension of you" scenarios: a launch lead, a scientist, a sales lead, a content creator. The first one describes my world almost exactly: You're a developer working on an app. Your dot watches customer feedback for recurring requests, scopes smaller improvements and bugfixes, builds and tests them, and brings you complete PRs to review with attached videos showing the changes. Read that again as a tech lead. The long tail of small fixes, like the copy tweak, the edge-case crash, or the "can we add a sort option" request, is exactly the work that never makes it into a sprint. It isn't hard. It just never beats the big feature for priority. If a dot can really turn that backlog into reviewable PRs with videos attached, my role moves further toward reviewer and editor. I'd keep building the next major feature, and the dot would work the queue. The key word in OpenAI's description is **review**. The dot brings me PRs. It doesn't merge them. To be clear, I haven't benchmarked this, and OpenAI doesn't publish benchmarks or success rates for it in the announcement. I'm treating it as a stated design goal, not a proven throughput number. Any agent with its own computer and access to 4,000+ apps should make an engineer nervous. OpenAI spends a big chunk of the announcement on safeguards, and they're more specific than I expected: On data, OpenAI says it doesn't use content from ChatGPT Business, Enterprise, or Edu workspaces to improve its models by default. On personal plans, you can control whether your dot's conversations and work are used for training. They also say they don't train directly on proactive research or your dot's notes to itself. And there's one line I want every engineer to tattoo somewhere: **"Dots can still make mistakes, so always review consequential work."** OpenAI points to a dedicated dots safety blog, its Help Center, and a system card for more detail. My take: this is the right shape. Default-deny for risky actions, read-only background mode, human approval for anything consequential, and a visible audit trail. It's basically how I'd want a new junior engineer onboarded: broad read access, narrow write access, and a reviewer on every merge. Beyond your personal dot, OpenAI is previewing **specialist dots**. These take on dedicated responsibilities inside an organization rather than working on behalf of one person. Per the announcement: This is starting with **focused enterprise pilots**, where OpenAI's engineering teams work directly with organizations to define each dot's responsibilities, the tools it can use, and how people review and approve its work. OpenAI is also working with **Microsoft** to integrate specialist dots with Microsoft's enterprise governance and security controls in **Agent 365**, so businesses can manage dots with the Microsoft tools they already use. For those of us who've fought with service accounts and shared credentials, giving an agent its *own identity* is a big deal. It means the audit logs can say "the procurement dot did this" instead of "someone using Dave's token did this." Here's the practical part, straight from the announcement: That usage-limit detail is easy to miss and worth planning around. Chatting with your dot is "free" against limits, but delegating real Codex work isn't. This is my own plan, not an OpenAI recommendation. If you lead a team, it might be a useful starting template: ``` Week 1 — dot onboarding plan (my notes) Day 1: Create the dot on desktop, name it, connect only Slack + GitHub + calendar Day 2: Set Custom Rules — require approval for anything that posts, merges, or emails Day 3: Let proactive research run; check Activity View at end of day Day 4: Hand it one small, well-scoped bugfix from the feedback backlog Day 5: Review the PR like a junior's PR; write feedback, not just approve/reject Weekend: Decide what to widen (or narrow) next week ``` The principle is the same one I use with any new teammate: start narrow, watch closely, widen access based on evidence. OpenAI has given us the controls (Custom Rules, Activity View, app permissions, auto-review). It's on us to actually use them instead of clicking "allow all." I've been burned by agent hype before, so here's where I land. **What I'm genuinely excited about:** persistence and isolation. An agent with its own inspectable computer, context that carries across ChatGPT, Slack, and Teams, and a read-only proactive mode is a real architectural step. It's not just a smarter prompt box. **What I'm cautious about:** everything that depends on the dot learning "what good looks like" for me. That's the hardest part to evaluate from an announcement. It will only prove itself through weeks of real review cycles. OpenAI's own advice to always review consequential work tells me they know that too. **What I'm not claiming:** I don't have numbers on speed, accuracy, or cost per task, and OpenAI didn't publish any in the launch post. Anyone quoting benchmarks for dots right now should show their source. The shift I expect is this: my job gets less about *doing* the long tail and more about *defining standards and reviewing output*. That was always the job of a good lead. Dots just make it hard to pretend otherwise. What would you hand your dot first: the bug backlog, the inbox, or the planning doc nobody updates? Tell me in the comments. I'm genuinely curious how other teams plan to onboard their first always-on teammate. *Originally published on [Medium](https://medium.com/@ishank.iandroid/chatgpt-dots-how-im-weaving-openai-s-latest-features-into-my-projects-eecbe6c1dafc).*