[AINews] OpenAI DevDay 2026: Dots, 6.1 Sol, Ultrafast, Decisions API, Agents API, Spaces, Marketplace, and 1.2 Billion ChatGPT WAU
- ID
- 30183
- Status
- summarized
- Published
- 30 Sep 2026, 1:53 PM
- Fetched
- 30 Sep 2026, 2:40 PM
- Provider
- Latent Space
- Category
- developer-ai
- Original URL
- https://www.latent.space/p/ainews-openai-devday-2026-dots-61
- Source URL
- https://www.latent.space/feed
Summary
- Score
- 7.5
- Created
- 30 Sep 2026, 2:40 PM
- Tags
- Audience
- developersai_agent_userssaas_foundersai_ml_learners
What happened
At OpenAI DevDay 2026, OpenAI launched Dots — always-on agents running on GPT-6 Astra, each with its own cloud computer, connections to 4,000+ apps plus Slack/Teams, and per-action boundaries (autonomous / needs approval / never) — alongside ChatGPT Spaces and Pages for shared human-agent workspaces. GPT-6.1 Sol is priced at $2/$10 per million tokens with cached input at $0.10 (a 95% cache discount), and OpenAI claims it ties Astra on DeepSWE, beats Opus 5.5 on AutomationBench at one-third the cost, lands 2.1 points behind Astra on OSWorld 2.0 at roughly one-seventh the cost, and cuts factual errors on hard prompts by ~32% versus 6 Sol. Dots ship to Pro, Business Premium and Enterprise, and the Decisions API launches as a light shim over Luna that gains vision but no calibration/RLCD.
Why it matters
The $0.10 cached-input rate is the number to re-run your cost model against — if your workload is cache-heavy, Sol's effective price per task can move by more than the headline $2/$10 split suggests. Also plan around the stated billing boundary: a dot's own direct work reportedly does not draw on plan usage, but the Codex tasks it spawns do, so agent-initiated bug triage, failing builds and PR handoffs are the line item that scales unpredictably. If you run a SaaS in one of the 4,000+ connected apps, decide now whether Dots are a distribution surface or a layer that sits between you and your users. Nothing in this text is Malaysia- or SEA-specific; treat it as a US vendor pricing and platform change.
Discussion angle
The Dots billing boundary: if a dot's own work doesn't consume plan usage but the Codex tasks it spawns do, how do you forecast spend before you let an agent autonomously open PRs and retry failing builds?