Introducing dots
- ID
- 29903
- Status
- summarized
- Published
- 29 Sep 2026, 8:00 AM
- Fetched
- 30 Sep 2026, 9:28 AM
- Provider
- OpenAI News
- Category
- ai-labs
- Original URL
- https://openai.com/index/introducing-dots
- Source URL
- https://openai.com/news/rss.xml
Summary
- Score
- 6.5
- Created
- 30 Sep 2026, 9:28 AM
- Tags
- Audience
- developersvibe_codersai_agent_usersstartup_founders
What happened
OpenAI announced dots: always-on agents powered by GPT-6 Astra, each with its own cloud computer and browser, plugin connections to over 4,000 apps, and reachability through ChatGPT, Slack, Teams, or a voice call. Dots are rolling out first on Pro, Business Premium, and Enterprise plans in unspecified "eligible markets," with a separate preview of specialist dots that get their own identity for access management, IT-provisioned hardware, and deep integrations with company systems of record. The post is a first-party product announcement with one named outside example: an early tester's dot drafted an invoice he had forgotten and sent it after his approval.
Why it matters
The enterprise detail is the one builders can act on: specialist dots get their own identity, IT-provisioned hardware, and access to systems of record — meaning agent seats may need to be provisioned, permissioned, and billed separately from human users in your product. If you sell SaaS into companies, expect procurement to ask how an agent authenticates and what it can touch; if you're in Malaysia, the text only says "eligible markets" and does not list them, so availability for your team is unconfirmed.
Discussion angle
If agents get their own identity and provisioned hardware, does your product's onboarding, permissions, and pricing model assume one seat equals one human? Walk through what would break first.