OpenAI has launched 'Dots' — its own getting-started guide indicates the 'dot' device is now in customers' hands — marking its first consumer hardware product, and whether the dot sustains adoption beyond DevDay launch-week novelty resolves whether OpenAI has gained a durable consumer hardware surface.

What is this?

Why it matters to Scott

Measured heat

How the heat travelled

Evidence (46) — ⭐ canonical anchor

September 29, 2026

[Product](https://openai.com/news/product-releases/)[Company](https://openai.com/news/company-announcements/)

# Introducing dots

[Create your dot(opens in a new window)](https://chatgpt.com/dots)[Contact sales](https://openai.com/contact-sales/)

Loading…

Share

**Dots are remarkably capable, always-on agents built to handle everything.** They’re a whole new way to work with AI—one that gets to know what matters to you, is always working on your behalf, and takes important work off your plate so you get more of your time and attention back.

Dots are frontier intelligence that have your back. Powered by GPT‑6 Astra, they have their own cloud computer, learn from feedback over time, and can work towards your goals 24/7. Through our ecosystem of plugins, they can readily connect to over 4,000 apps, giving them the tools to help wherever you need them.

Your dot is always within reach, whether it is through ChatGPT, Slack, or Teams. You can ask questions, explore ideas, and give feedback along the way; or you can simply hop on a voice call when you need to talk something out. The more you work together, the more your dot learns your preferences, how you think, and what good looks like to you.

The magic of dots is when they bring you work done the way you would do it, sometimes before you even think to ask. With dots alongside you, ambitious ideas and projects you haven’t had the time or support to pursue start to feel achievable.

Inside OpenAI, we’re getting a glimpse of what work looks like when intelligence is always working by your side. A bug appears in Slack, and dots immediately start investigating. A new design arrives, and dots turn it into a working app while the team focuses on customer feedback. A planning cycle gets underway, and dots keep everyone moving in sync toward the deadline. Outside OpenAI, an early tester’s dot noticed he’d forgotten to invoice a publication, prepared the invoice, and sent it after his approval.

Today, you can start with your primary dot, give it a name, and make it your own. Over time, we envision teams of dots working together on your behalf. We’re beginning to roll out dots across Pro, Business Premium, and Enterprise plans in eligible markets. We plan to expand dots to more users soon. We’re also sharing a preview of specialist dots with their own identity for access management, IT-provisioned hardware, and support for deep integrations with a company’s systems of record to allow them to take on well-defined responsibilities inside organizations.

## Dots can work on their own

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. Dots can connect to other devices in addition to their own and you can also give your dot permission to connect and use your laptop, where it can then be useful directly alongside you.

Your dot can take a project and run with it, even while it’s working on several others. You can keep bringing it new tasks and ideas without having to juggle separate threads or direct every step.

## Dots are an extension of you

With a dot that knows your goals and standards, you can take on more without directing every step. Here’s what that looks like:

Pink dot Iggy prepares an iOS beta checklist fix beside a release workspace.

**Turn feedback into tested fixes**

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. You can keep building the next major feature while reviewing the fixes and improvements your dot prepares.

Blue dot Felipe revises launch materials beside two email and social design options.

**Revise a launch as scope changes**

You’re leading a product launch. Your dot learns your audience, positioning, and creative standards. When the product scope changes, it works through what that means for the story, revises the launch materials, and prepares drafts of asset and doc changes. You return to a launch plan and creative work shaped by the direction you’ve set, ready for your review.

Green dot Todd discusses repeat test findings beside an email draft and comparison chart.

**Update analysis with new evidence**

You’re a scientist. Your dot learns your research question and how you evaluate evidence. As new data arrives, it reruns analyses, investigates unexpected results, and updates the figures for your paper. When findings change, it revises the supporting explanation and flags what needs your review. You return from the lab to work that reflects the latest evidence.

Yellow dot Alfred discusses an enterprise proposal beside a document listing steps to close the deal.

**Update a proposal as requirements shift**

You’re a sales lead guiding an enterprise deal through technical review. Your dot checks customer requirements and account history against product docs, finds what still needs testing, builds a proof of concept for a key integration, and suggests a solutions engineer who’s handled a similar deal. As requirements and test results change, it updates the proposal and test plan and flags open concerns. You and your engineer focus on customer conversations and approve commitments.

Purple dot Jojo helps a creator prepare an interview post beside a social image.

**Automate content production work**

You’re a content creator. Your dot learns your voice and what matters to your audience. When a new interview transcript arrives, it identifies moments for clips, prepares show notes, and drafts social posts for your approval. It carries your edits across the materials and learns what resonates—giving you more time to create.

## Dots work where you work

Working with your dot is as simple as having a conversation. You can message or call dots in ChatGPT on desktop, web, and mobile. They can also message you with progress, questions, or decisions that need you.

You can also message your dot in Slack and Teams, with texting coming soon. Start a project in ChatGPT, share context with the working team in Slack, and let your dot follow through. Dots carry context across every channel, so your dot will have the full context wherever you reach it.

## You’re always in control

Dots build on ChatGPT’s protections with [additional safety and privacy safeguards](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/) for the work they can do. You can set boundaries, follow progress, and stay involved in decisions that need you.

### Built-in safeguards

Each dot works on its own cloud computer, while your computer and its contents stay separate unless you choose to connect it. For signing into supported websites, dots can use saved passwords without exposing them to the model.

When you aren’t actively working with it, your dot looks for ways to help in the background. We call this “proactive research”. It does this by using the apps you’ve already connected with tools that are restricted to be read-only, which means that they can’t send messages, change app content, or control your browser or computer.

Security safeguards built into dots help defend against malicious instructions and monitor for potentially harmful behavior. If our monitoring system detects a safety concern, it can pause or stop the dot’s work.

### Access and permissions

You choose which apps dots can access and can manage their permissions through your existing ChatGPT app controls.

Dots start with built-in rules for when to act independently and when to ask for approval. Custom Rules let you allow specific actions, require approval, or block them. Built-in safety requirements always apply and you can follow progress, including background work, in Activity View and redirect dots as needed.

We don’t use content from ChatGPT Business, Enterprise, or Edu workspaces to improve our models by default. On personal ChatGPT plans, you can control whether dots’ conversations and work are used to [improve our models⁠(opens in a new window)](https://help.openai.com/articles/7730893-data-controls-in-chatgpt). We don’t train directly on proactive research or your dot’s notes to itself. Information from them may be used if it helps inform an eligible conversation or task, depending on your settings.

### Action review and approvals

Dots use [auto-review⁠(opens in a new window)](https://learn.chatgpt.com/docs/sandboxing/auto-review) to check actions that could affect your accounts or share information against your instructions, Custom Rules, and safety requirements. This helps determine what work can proceed, what needs approval, and what you must do yourself. Certain sensitive tasks, such as changing a password, always stay with you.

You can learn more about our safety approach for dots in [our dots safety blog](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/), in our [Help Center⁠(opens in a new window)](http://help.openai.com/articles/20001529), and in our [system card⁠(opens in a new window)](https://deploymentsafety.openai.com/gpt-6-astra/change-log). Dots can still make mistakes, so always review consequential work.

## Specialist dots for your organization

Your dot works on your behalf; **specialist dots** take on dedicated responsibilities within your organization. Your company sets up each dot with its own identity, credentials, and access to the systems it needs to complete its tasks. As it works, the dot adapts to new information and improves with feedback from your team. We’re building on lessons from early testing inside OpenAI across procurement, invoice processing, email marketing, customer support, and commercial contracting.

We’re starting with focused enterprise pilots. Our engineering teams will work directly with organizations to define each dot’s responsibilities, the tools it can use, and how people review and approve its work. If there’s work you’d like a specialist dot to take on, we’d like to hear from you.

### Bringing specialist dots to Microsoft Agent 365

We’re also working with Microsoft to integrate specialist dots with their enterprise governance and security controls in Agent 365. The goal is to let businesses manage dots through the Microsoft tools they already use.

## Get started with dots

Dots are rolling out today in ChatGPT to Pro and Business Premium users in [eligible markets⁠(opens in a new window)](https://help.openai.com/articles/20001530). Enterprise users (including Edu and Healthcare) can try the beta when their workspace admin enables it.

Your first dot is included in your Pro or Business Premium plan at no extra cost. It’s available 24/7 to talk, help you think, and stay on top of what matters to you. Your plan also includes an allowance for deeper work, with extended limits for the first month after launch. In the future, you’ll be able to add more dots, and scale the output of each dot by either increasing its speed or the total amount of work it can take on per month.

Conversations with your dot don’t count toward your ChatGPT usage limits. When you ask your dot to start or manage tasks in Codex or ChatGPT Work, those tasks count toward your usage limits as usual.

To get started, create your first dot in the ChatGPT desktop app or your desktop browser, connect your apps, and let it introduce itself. After the initial setup, you’ll be able to message it in the ChatGPT mobile app.

We’ll keep improving dots as we learn what makes them useful every day. We’ll share what we learn where we can and use it to guide what we build next.

- [2026](https://openai.com/news/?tags=2026)
- [ChatGPT](https://openai.com/news/?tags=chatgpt)
- [ChatGPT Work](https://openai.com/news/?tags=chatgpt-work)
- [Enterprise](https://openai.com/news/?tags=enterprise)

## Author

OpenAI

## Keep reading

[View all](https://openai.com/news

Interpretation history

• 2026-10-10T17:43:12Z
  Reliability cluster gains a fifth independent breakage report (delegation/sub-chat feature broken after update) but each report remains uncorroborated; the Oct 29 carve-out expiry (~19 days out) remains the binding clock with no new terms announced; measured heat stays cold (1.0 pts/h, steady, p73) despite magnitude-valve-eligible cross-platform spread — the periphery expands but each addition is thin.
• 2026-10-10T15:42:12Z
  evidence attached: reddit.post.1x2gqnc — Early adopter reports Dot's delegation/sub-chat feature broke after an update — real-world breakage evidence for the launched hardware.
• 2026-10-10T10:55:57Z
  Reliability cluster gains a fourth independent report (403 errors and browser crashes on the cloud computer) but each report remains uncorroborated; the Oct 29 carve-out expiry (~19 days out) remains the binding clock with no new terms announced; measured heat stays cold (0.33 pts/h, steady, p60) despite magnitude-valve-eligible cross-platform spread — the periphery expands but each addition is thin.
• 2026-10-10T10:33:16Z
  evidence attached: reddit.post.1x2b9s4 — User-reported 403 errors and browser crashes on Dots cloud computer, relevant to launch-week adoption friction.
• 2026-10-10T00:34:04Z
  New power-user feedback (1x1sfy7) is too early (1 upvote, 7 comments, uncorroborated) to shift the case's meaning; the Oct 29 carve-out expiry (~2 weeks out) remains the binding clock. Measured heat confirms cold tail (0.17 pts/h, steady, p47 cohort) despite magnitude_valve_eligible cross-platform spread — the periphery expands but each addition is thin. Case stays dense dated-receipt material for Scott's canon (token-burn economics, cap mechanics, auto-review, deleted-content resurfacing, OpenClaw comparison).
• 2026-10-09T19:58:37Z
  evidence attached: reddit.post.1x1sfy7 — Power-user feedback on Dots hardware experience — material user evidence for the case tracking whether the device sustains adoption beyond launch novelty.
• 2026-10-08T21:02:38Z
  A claimed 24-hour stress test (1x0qf1x) adds to the execution-model evidence pile but is too early (1 upvote, 0 comments, uncorroborated) to shift the case's meaning; the tail remains cold (0.17 pts/h, p53 cohort) with only the week-old token-burn post drifting. The Oct 29 carve-out expiry (~3 weeks out) is still the binding clock — curtailment is already live via opaque, workload-shape-dependent caps while advertised terms lag. Reliability cluster (wipe, deleted-content resurfacing, unresponsiveness) hardens at pattern level but per-report uncorroborated. Adoption stays bifurcated with receipts on both sides.
• 2026-10-08T17:49:19Z
  evidence attached: reddit.post.1x0qf1x — A claimed 24-hour stress test is early hands-on evidence about how OpenAI Dots actually executes tasks, relevant to whether the new hardware surface proves durable and usable.
• 2026-10-07T23:34:27Z
  The launch tail crossed the low-heat threshold the last reprice set: case rate ~1.3 pts/h against a 758 peak with no new participants, communities, or outlets — the token-burn post's residual upvote/comment drift is the only motion, and the p84 cohort percentile just says most 9-day-old peers are dead. The new unresponsiveness report (1x0b7n2, incl. an uncorroborated GPT-Live-1 API-failure claim) folds into the existing reliability cluster without changing the case's meaning; everything now waits on the Oct 29 carve-out expiry.
• 2026-10-07T23:27:06Z
  evidence attached: reddit.post.1x0b7n2 — Launch-week reliability complaints (device answering once since launch, top comment claiming GPT-Live-1 API calls frequently fail) are direct evidence on whether the Dot sustains adoption.
• 2026-10-07T06:58:43Z
  grounded: converges/high — OpenAI — the most consequential party available — shipped the consumer-scale version of Scott's Give-the-Agent-a-Workshop thesis, and the teardowns confirm his
• 2026-10-07T06:50:05Z
  Third independent abuse-cap report (1wznf8g) plus a staff-sounding quote conceding 'virtually unlimited' is momentary — and an uncorroborated Pro-200 20x-to-10x halving line — shifts the case's meaning from 'will OpenAI curtail after Oct 29?' to 'curtailment is already underway via opaque caps while advertised terms lag reality.' The renewed velocity spike is the token-burn post (1wyoaw7, now 563/211) amplifying a fully priced story; heat holds at medium only because the hottest object is still a p95.5 four-platform cohort mover and the decisive Oct 29 terms clock is ~3 weeks out — a further halving of the tail with no new participants drops this to low.
• 2026-10-07T06:29:22Z
  evidence attached: reddit.post.1wznf8g — Top users hitting abuse-prevention cooldowns on a dot marketed as 'virtually unlimited' is material post-launch erosion of the device's core promise.
• 2026-10-06T18:44:08Z
  The silent credit-drain report (1wz4ukp) is the same author's second failure post and folds into the existing billing-friction cluster — its Codex-session mechanism matches documented OpenAI behavior (Codex tasks count against allowances; credits auto-consume when limits drain), so nothing in the case's meaning moved. Launch tail keeps cooling (case rate ~14 pts/h vs 741 peak) but the token-burn post stays a top-decile cohort mover and the ~Oct 29 terms clock remains the decisive event; heat holds at medium.
• 2026-10-06T16:42:15Z
  evidence attached: reddit.post.1wz4ukp — Documented silent credit drain on the dot device (top comment explains Codex-session mechanism) is concrete adoption friction the case's novelty-vs-durability judgment must weigh.
• 2026-10-06T15:18:37Z
  Velocity spike is amplification, not new substance: the 1.6B-token burn post (1wyoaw7) nearly tripled to 416/158 and the caps thread (1wy96in) climbed to 404/93, but no new fact, community, or implementation joined — the unit-economics contradiction and workload-shape-dependent caps were already priced. The sole new evidence (1wyy7mh, 0/4: dot can't run basic commands on a connected laptop, schedules burning main tokens) is one thin uncorroborated complaint folding into the consolidated mainstream-friction cluster; heat holds at medium because the deterministic 4-platform magnitude spread and a p94.4 hottest object keep attention genuinely warm ahead of the ~Oct 29 terms clock, even as the case-wide rate has cooled to ~19 pts/h from a 741 peak.
• 2026-10-06T11:33:25Z
  evidence attached: reddit.post.1wyy7mh — Early hands-on failure report on the dot device (can't run basic system commands, schedules burning main tokens) is concrete adoption-deficit evidence for the launch-durability case.
• 2026-10-06T04:58:44Z
  The 1.6B-tokens/day autonomous Dot (1wyoaw7, 129/68) turns the adoption bifurcation into a priced contradiction: a second independent attestation of multi-billion-token-per-day sustained real work on Pro-100 (alongside 1wxh6ky's 4B/2days) makes the unlimited carve-out month arithmetically unsustainable, and shows the abuse caps are workload-shape-dependent rather than flat — a Pro-100 email-assistant user hits the cap (1wy96in, now 346/82) while a CAD-engineering swarm escapes it. That sharpens the ~Oct 29 post-carve-out terms announcement into the case's decisive event: the terms must either kill the heavy-user pattern or absorb enormous losses. Heat holds at medium — the 4-platform magnitude spread is a cooling launch tail across already-covered platforms (momentum cooling, p96.6 residual), and the periphery (OSS clones, outlets, new communities) is still not expanding.
• 2026-10-06T03:33:52Z
  evidence attached: reddit.post.1wyoaw7 — A Dot running autonomously since launch burning ~1.6B tokens/day on real engineering output is direct sustained-adoption evidence — and a unit-economics problem — the Dot case must weigh.
• 2026-10-06T01:46:43Z
  The adoption picture bifurcates: alongside the consolidated mainstream friction and two-tier cap attestations, the first standalone third-party showcase (HN 49971444 — Dots run as an agent swarm proving new math, Lean-verified, free during the carve-out) gives the heavy-user cohort a public receipt matching the 4B-token claim, so durability is no longer uniformly negative-tilted. Heat rises to medium because the Pro-100 caps thread (1wy96in) is a genuine p94 mover with accelerating momentum and 4-platform magnitude spread — a substantive consumer-grievance story, not launch novelty — though the periphery (OSS clones, outlets, communities) still isn't expanding, so not high.
• 2026-10-05T23:34:21Z
  evidence attached: hn.story.49971444 — Early third-party report of Dots driving real work (agent swarm, Lean-verified proofs) — exactly the adoption evidence this case tracks.
• 2026-10-05T16:05:06Z
  The metering preview generalizes: after the Pro-200 stress-tester hit the abuse cap (1wxxrnm), a Pro-100 user now hit it on the product's own advertised assistant workload (1wy96in), so the 'unlimited' carve-out is read as opaque ceilings on ordinary agentic use at both paid tiers — post-Oct-29 terms will likely bite normal users, hardening the negative adoption tilt. The velocity and magnitude signals (focal thread at p93.8, 4-platform spread) are launch-tail coasting across already-covered platforms with no periphery expansion, so heat stays low.
• 2026-10-05T15:30:48Z
  evidence attached: reddit.post.1wy96in — First notable launch-window friction report (36/24 engagement): users wiring Dot into real account automation hit Pro-plan limits — early adoption-and-metering evidence the dot episode's re-judgment needs.
• 2026-10-05T03:36:06Z
  The case's main clock acquired its first empirical preview: OpenAI's abuse-prevention cap already throttles heavy Pro-200 users during the 'unlimited' carve-out month with opaque thresholds and no workload controls (1wxxrnm), so the post-Oct-29 regime is likely capped ceilings and the negative adoption tilt hardens; the ~500px browser-resize floor shared with Muse is a footnote to the settled commodity-VM picture. The velocity trigger is just the focal thread coasting above cohort p90 (62nd percentile) at 1.7 pts/h case-wide with no periphery expansion — decay, not re-ignition, so heat stays low.
• 2026-10-05T03:24:00Z
  evidence attached: reddit.post.1wxxfyi — Web developer finds Dots (and Muse) VMs can't resize browsers below ~500px, a concrete agent-environment capability limit relevant to judging the device's real workloads and Muse's.
• 2026-10-05T03:24:00Z
  evidence attached: reddit.post.1wxxrnm — First-hand early-user report of Dots hitting abuse-prevention throttling with no workload controls and a 'not ready for serious use' verdict — direct adoption/usability evidence for the case's durability question.
• 2026-10-04T22:00:23Z
  The rollout-coverage cluster extends to a Pro 5X payer with no Dots visibility at all (1wxq74j) — consistent with OpenAI's own phased-rollout language rather than a new failure mode — while the focal negative thread (178 pts) and teardown (508 pts) tick single-digit points. The magnitude-valve spread reading prices as launch-week residue coasting at ~4 pts/h (~0.6% of peak) with no new communities, outlets, or implementations: decay, not periphery expansion. The case's meaning is unchanged; it now waits on the Oct 29 allowance-terms expiry and corroboration of the wipe/deleted-content/outage reports.
• 2026-10-04T21:24:13Z
  evidence attached: reddit.post.1wxq74j — Direct case evidence: a paying Pro 5X user reports no Dots access, a rollout-coverage data point for the adoption hypothesis.
• 2026-10-04T15:27:14Z
  The reliability axis consolidates without yet corroborating: an unresponsiveness cluster (1wxh6ky, 28 comments, likely backend-side) joins the wipe and deleted-content reports as a third distinct reliability complaint, hardening the pattern-level 'unreliable infrastructure' reading, while a contested subagent-usage claim (7 subagents/4B tokens at no allowance cost vs. another user's Codex billing blowup) adds an allowance-economics ambiguity that feeds directly into the Oct 29 terms clock. The single-thread surge that priced medium has cooled to 4.3 pts/h (~0.7% of peak) with no new communities or outlets — the magnitude-valve spread is launch-window front-page residue (HN 764, CFO-flub 610, teardown 498 all date to launch week) — so heat returns to low.
• 2026-10-04T15:23:03Z
  evidence attached: reddit.post.1wxh6ky — Early broken-device reports and a power-user's heavy-usage/subagent claims are adoption-trajectory evidence the Dot case will need when re-judged.
• 2026-10-04T07:43:42Z
  The focal negative hands-on (1wwur33) has re-accelerated into the case's dominant post-launch object — 16x peer-baseline velocity, 84th percentile, 133 pts/85 comments — converting the adoption negative-tilt from three isolated single-source reports into one community-validated focal thread whose countervailing voices have also sharpened (notably a phone-first user for whom a hosted always-on agent removes the keep-a-machine-running burden, the one honest differentiator vs OpenClaw). This consolidates the durability outlook's negative tilt without changing the case's structure; the measured re-surge (7.5 pts/h case-wide vs 0.17 at last look, momentum cooling) prices medium heat where full decay priced low, scoped to a single thread so not high.
• 2026-10-04T07:23:36Z
  evidence attached: reddit.post.1wx8x9q — Substantive privacy/control objections with memory-visibility demands are early adoption-friction evidence bearing directly on whether the dot sustains adoption.
• 2026-10-03T19:53:51Z
  grounded: converges/high — OpenAI — the most consequential party available — has shipped the consumer-scale productization of Scott's Give-the-Agent-a-Workshop thesis, and the settled tea
• 2026-10-03T19:44:55Z
  Third negative hands-on (1wwur33) consolidates the adoption outlook's negative tilt — three-for-three negative first-person reports, each low-traction and single-source, with mixed in-thread countervailing voices — without changing the case's meaning: launch and architecture are settled and durability remains a clock toward the ~Oct 29 carve-out expiry. Engagement has fully decayed (0.17 pts/h vs 598 peak, 42nd percentile at ~116h, new submissions at 1-2 pts); the magnitude flag is launch-window front-page residue with no expanding periphery, so low heat stands.
• 2026-10-03T19:26:18Z
  evidence attached: reddit.post.1wwur33 — Pro-user hands-on reporting the dot consistently fails basic connectivity and tasks — early negative adoption evidence for the durability-beyond-launch question.
• 2026-10-02T20:21:11Z
  The new first-hand report that dot sessions receive deleted/unrecorded ChatGPT conversation content (1ww02y0) turns 'one flaky reliability report' into an early-forming trust-reliability pattern alongside the uncorroborated environment-wipe claim — a strengthening of the existing negative tilt, not a change in the case's meaning: launch and architecture are settled, and the case remains a time-gated adoption watch toward the ~Oct 29 carve-out expiry. Velocity has cooled ~4x since the last look (31→7.7 pts/h); the magnitude flag and 83rd percentile are aged front-page accrual on settled objects while new submissions land at 1 pt and the clone periphery is not expanding, so low heat stands.
• 2026-10-02T19:29:57Z
  evidence attached: reddit.post.1ww02y0 — Concrete first-hand report that Dot sessions receive deleted/unrecorded ChatGPT conversation content — an early privacy-trust signal bearing directly on the new device's adoption prospects.
• 2026-10-02T15:43:41Z
  No new fact this look: hn.story.49934474 ('What Dots Choose: OpenAI's Agent Has a Stack') is a 1-pt/0-comment stack-analysis post adding nothing beyond the existing teardown characterization, and the velocity flag is the 87h-old teardown thread accreting ~5 pts/h. Case meaning unchanged — settled launch and architecture, negative-tilted adoption watch on the ~Oct 29 carve-out clock; the magnitude-valve and 83rd-percentile readings are front-page residue on four launch-week objects accreting <10 pts/h combined, with no new communities, implementations or outlets entering, so low heat stands despite the loud spread flag.
• 2026-10-02T15:25:28Z
  evidence attached: hn.story.49934474 — First post-launch teardown of the dot device's agent stack materially contextualises the OpenAI consumer-hardware episode.
• 2026-10-02T02:05:09Z
  The 1wvew89 finding collapses the product's last architectural mystique: dots are thin clients over hidden Codex Cloud threads, so the 'own computer' is repurposed dev-sandbox infrastructure rather than a new always-on agent substrate. That coheres the negative sentiment ('reskin of Codex/ChatGPT Work', 'a worse OpenClaw') into one story — OpenAI's consumer agent surface is consumer-packaged Codex Cloud with persistent-agent framing — which is itself a sharper data point for Scott's workshop thesis (the workshop is a rented commodity VM). The loud speedometer (31 pts/h, 94.6 percentile, magnitude flag, 'accelerating') is a single 74h-old teardown post accreting 328→349 plus settled front-page residue; every new object across HN and Reddit lands at 1-2 pts and the toy clones still have zero traction, so the periphery is not expanding and low heat stands. Case remains a time-gated adoption watch toward the ~Oct 29 carve-out expiry.
• 2026-10-02T01:27:07Z
  evidence attached: reddit.post.1wvew89 — First-hand discovery that dots are thin clients over hidden Codex Cloud threads (send_message, invisible sessions) materially characterizes what OpenAI's consumer hardware surface actually is.
• 2026-10-01T22:16:58Z
  The new privacy alarm (1wv8074) resolves as thin: its own comment thread points to user-granted broad repo scope rather than an agent-initiated boundary crossing — thematically consistent with the trust-qualm cluster but corroboration of nothing, and it would only become material if confirmed as access outside granted scopes. Case meaning unchanged: settled launch, negative-tilted durability question on a ~Oct 29 clock; the loud magnitude/96th-percentile readings are again 70h-old front-page residue (settled CFO-'Muse' and main-thread accrual, new objects single-digit), so heat holds low.
• 2026-10-01T20:35:47Z
  evidence attached: reddit.post.1wv8074 — Unverified but direct trust/privacy alarm on the Dot device itself, material context for its post-launch adoption trajectory.
• 2026-10-01T15:25:57Z
  Refinement, not turn: the two new attachments soften the adoption picture at the margin — a third, technically credible hands-on (1wuznlr) documents the execution model and real long-running workloads working as described, and the founder-encroachment thread carries an isolated power-user positive (dots absorbed into a six-agent home lab) — moving the outlook from uniformly negative to negative-tilted while leaving the verdict open. The velocity spike is again the settled CFO-'Muse' post's tail (574 pts); every new object lands single-digit, so the loud magnitude/percentile readings are front-page residue, not spread — heat stays low and the case remains a time-gated adoption watch toward the ~Oct 29 carve-out expiry.
• 2026-10-01T14:32:26Z
  evidence attached: reddit.post.1wuznlr — Early hands-on teardown documents the Dot's persistent cloud execution model and real long-running workloads — exactly the beyond-launch-novelty adoption evidence the open case hinges on.
• 2026-10-01T14:32:26Z
  evidence attached: reddit.post.1wuzygv — Founder reaction adds material adoption context on Dots' scope (always-on agent, 4,000+ connectors, tier gating) and the platform-encroachment question around the DevDay agent stack.
• 2026-10-01T11:56:37Z
  The EU exclusion — a pillar of the gating story — picks up its first crack: a European business account reports dot access (1wuw9z4), matching a business-tier exception already visible in the EU-exclusion thread, so the regional lockout reads as a staged rollout (business tier first) rather than an absolute wall — a gating refinement, not a turn. Everything else is decay: the velocity spikes are the settled CFO-'Muse' mockery post accruing (448→527→561), new objects land single-digit, and the adoption verdict (two negative hands-ons, the still-uncorroborated environment-wipe report) is unchanged — the case stays a time-gated adoption watch, not materially advanced by a 21-point single-user report.
• 2026-10-01T11:26:10Z
  evidence attached: reddit.post.1wuw9z4 — First reported European availability (business accounts) is rollout-spread context a re-judge of the dot's durable-adoption case would need.
• 2026-09-30T23:12:31Z
  Decay tick, not a turn: the 'substantive' object that re-fired the sensor is a fourth open-source clone (Open Dot, 1 pt / 0 comments), reinforcing that the ecosystem response is a trickle of stunts rather than serious counter-implementation; the 93rd-percentile velocity and 4-platform magnitude reading are the two-day-old front-page thread's comment tail, not new-object motion — new items land single-digit, so heat stays low despite the loud speedometer. No new hands-ons, the environment-wipe report remains single-source and uncorroborated: the case's meaning is unchanged, and the adoption verdict stays a time-gated watch, not yet resolvable.
• 2026-09-30T18:42:40Z
  evidence attached: hn.story.49912211 — An open-source ecosystem counter-project to OpenAI's Dot device is adoption-and-ecosystem context the case's re-judgment should weigh.
• 2026-09-30T17:32:19Z
  The first-party 'Introducing dots' text lands as canonical confirmation: dots officially ship on GPT-6 Astra (largely dissolving the WSJ-scrapped-model tension into 'a scrapped internal 6.1 variant'), and the carve-out is clarified — conversations never count against plan limits while the month-one extension covers the deeper-work allowance, with future monetization via extra dots and per-dot speed/work scaling, plus specialist dots (own identity/credentials) heading into enterprise pilots under Microsoft Agent 365 governance. The adoption verdict is untouched — negative hands-ons stand, the environment-wipe report remains uncorroborated — and heat stays low: ~62 pts/h against a ~483 peak and cooling, the 4-platform magnitude reading being front-page decay (single-digit new items, clone attempts stalled, the 241-pt CFO-said-'Muse' post is settled mockery, the velocity spike an old EU post's comment tail).
• 2026-09-30T17:30:09Z
  evidence attached: openai.article.39c7a6b043327be1d35e74ff — shared external link with case evidence
• 2026-09-30T16:17:03Z
  The negative hands-on picture is now multi-source and multi-failure-mode: a second independent review reports slowness, no progress feedback, failed email monitoring and — cutting at the workshop premise itself — an agent that seems barely to use its 'computer', while the environment-wipe report remains single-source and uncorroborated; the redundant EU-exclusion post adds nothing. The magnitude-valve spread reading is front-page decay (48 pts/h vs ~483 peak, cooling, new items single-digit, open-source clones stalled at toys), so heat stays low.
• 2026-09-30T15:27:10Z
  evidence attached: reddit.post.1wu77gv — Detailed first-hand negative usage review (slowness, no computer use, failed email monitoring) is early-adopter evidence the adoption-resolution case must weigh.
• 2026-09-30T15:27:10Z
  evidence attached: hn.story.49909778 — shared external link with case evidence
• 2026-09-30T14:49:04Z
  The persistence promise at the core of the dot's premise just took its first direct field hit: a hands-on user reports the dot's cloud environment wiped his synced project data within hours of setup, the dot itself confirming a fresh environment. Single-source and uncorroborated, but it converts 'persistence' from an assumed feature into the case's central reliability question and tips the already negative-slanting adoption outlook further down; heat stays low — velocity is ~91% off peak and cooling, and the new item has zero traction (1/0), so the magnitude reading remains front-page decay residue.
• 2026-09-30T14:25:24Z
  evidence attached: reddit.post.1wu5zrb — First-hand report of dot cloud environment wiping user data bears directly on whether the dot sustains adoption beyond launch novelty.
• 2026-09-30T11:52:46Z
  First teardown pins the dot's 'own computer' as a commodity cloud VM (EPYC, 9 vCPU, ~10GB RAM, no GPU) — a thin client, sharpening the workshop-thesis meaning: the agent's computer is a cheap rented sandbox, not a new compute surface — while the launch-stumble cluster (broken demo, Grok search redirect, CFO saying 'Muse' on air) deepens an already negative-slanting reception. With velocity ~90% off peak, momentum cooling, and the periphery stalled at toy clones plus same-community single-digit ripples, the 98.9-percentile/magnitude readings are front-page decay residue rather than active spread; heat cools to low and the live questions (post-carve-out terms, Pro 100 breadth, EU availability, retention) resolve on day-to-week timescales, not hours.
• 2026-09-30T11:24:57Z
  evidence attached: reddit.post.1wu1sue — First concrete teardown of the Dot's execution environment (EPYC-hosted cloud sandbox, no GPU), revealing the device as a thin client — useful technical context for the case.
• 2026-09-30T11:24:57Z
  evidence attached: reddit.post.1wu22ql — Concrete launch failures — demo broke on livestream, search misdirection, CFO misnaming the product — material context for whether the dot becomes a durable hardware surface.
• 2026-09-30T10:47:08Z
  The substantive_evidence re-fire is on the Stratechery piece already attached last cycle and its thread is inert (1 pt / 0 comments, unchanged) — no new fact arrived, so no material change; the only shift is absorption of Ben Thompson's 'model-company-to-product transition' framing as analyst-class corroboration of the Dot's strategic significance, which doesn't touch the still-open adoption verdict. Heat holds at medium on the 98th-percentile residual velocity and the time-gated open questions despite the loud spread reading: the periphery (three toy clones, one inert essay) is no longer expanding with traction, and everything live resolves in days, not hours.
• 2026-09-30T10:24:59Z
  evidence attached: hn.story.49906766 — High-authority Stratechery analysis of the Dot within OpenAI's DevDay product transition is material context for judging durable consumer-hardware adoption.
• 2026-09-30T08:54:52Z
  Melete (1 pt, 0 comments) is the third open-source clone inside launch week and confirms the toy-traction stall rather than changing anything — the periphery is adding names, not traction, and no influential entrant has followed. Velocity keeps decaying (~89% off peak) while the main HN thread still sits at ~97th percentile for its cohort; heat holds at medium on that residual velocity plus the pending time-gated questions, and the loud magnitude-valve spread reading is acknowledged but outweighed by a story 16h past crest. Meaning, state and relevance are unchanged: settled launch, negative-slanting reception, adoption watch.
• 2026-09-30T08:25:10Z
  evidence attached: hn.story.49905773 — An open-source alternative to the Dot appearing within launch week is direct competitive context for whether the device sustains durable adoption.
• 2026-09-30T05:56:52Z
  The velocity spike is the main HN thread crossing 500 points — engagement, not new meaning; the substantive_evidence flag re-fires on the hands-on post already attached and absorbed last look. The implementation periphery that justified 'accelerating' has stalled at toy traction (Open Dots 3 pts, Thursday downvoted to 0), so the case steps back to corroborated: launch, gating, and reception are settled facts, and everything still live — creation failures at scale, post-carve-out terms, Pro 100 breadth, EU availability — resolves on days-to-weeks of clock time, not momentum.
• 2026-09-30T05:26:12Z
  evidence attached: reddit.post.1wtw0f1 — Early hands-on use of the dot with concrete capability gaps (no calls, no feedback channel) and sandbox specs — directly relevant to whether it sustains adoption beyond launch novelty.
• 2026-09-30T04:29:06Z
  Launch-week reception has landed and slants negative: paying Pro-200 holders frame the dot as a locked-down downgrade vs OpenClaw, EU exclusion anger is hardening into visible churn intent, and open-source responses (Open Dots, Thursday) spawned within hours — each thin alone, but the periphery is still expanding while the core wave crests. Heat steps down high→medium because momentum is cooling ~87% off peak and the live questions (creation failures, retention past the month-one carve-out, Pro 100 breadth) resolve on days not hours; that is the counterweight to the magnitude-valve spread reading, and the case stays accelerating on implementation spread rather than velocity.
• 2026-09-30T03:31:24Z
  evidence attached: reddit.post.1wttl9b — Early negative reception — dot seen as a worse, more locked-down OpenClaw at higher effective cost — is direct evidence on whether the dot sustains adoption.
• 2026-09-30T03:31:24Z
  evidence attached: reddit.post.1wtubb9 — Launch-week open-source competitor comparison that concretely contextualizes what Dots actually offer (Pro-gated, cloud-only, app catalog) versus local-first alternatives.
• 2026-09-30T02:24:45Z
  The gating question is settled by the fresh grounding — Dots are always-on software agents, not hardware — so the case's live question is now purely adoption, and this look supplies its first hands-on data: paying Pro-200 users blocked at creation by region/eligibility errors, one working user confirming buggy-but-real multi-PC execution, and docs indicating Pro 100 access is coming. That narrows the case from 'what is it' to 'can eligible users actually use what they paid for, and will they stay past the free first month.'
• 2026-09-30T00:38:31Z
  evidence attached: reddit.post.1wtojni — Early real-user rollout friction — dots gated behind a Pro-200 upgrade then failing to create — is direct adoption evidence for the accelerating dot case.
• 2026-09-29T23:16:11Z
  grounded: converges/high — OpenAI's DevDay pitch — 'give an agent its own computer and a goal, and it keeps working while you're gone' — is Scott's Give the Agent a Workshop / Self-Equipp
• 2026-09-29T23:08:23Z
  The epistemics flipped: what the grounding treated as an echo-only shipping claim (no web mention of 'Dots', a 2027 io-delay report cutting against it) is now corroborated by independent testimony across HN and several subreddits agreeing on concrete mechanics — top-plan gating, EEA/UK exclusion, one-month allowance carve-out. But the discussion's texture (plan allowances, 'an agent with its own computer', blur with Codex/ChatGPT Work, cute-avatar privacy qualms) reads as an always-on software agent, not the physical device the case's frame assumes, so device-vs-agent is now the question that gates the case's meaning and the cached grounding is misleading.
• 2026-09-29T20:53:12Z
  evidence attached: hn.story.49897710 — An immediate open-source clone shows developer ecosystem reaction around the dot launch — material context for the adoption question.
• 2026-09-29T20:53:12Z
  evidence attached: reddit.post.1wth5vv — DevDay 'give an agent its own computer' pitch echoing at 85/30 on r/singularity is launch-week reception evidence the dot case should carry.
• 2026-09-29T20:53:12Z
  evidence attached: reddit.post.1wthgk0 — Concrete launch-week adoption friction — high pricing and EU unavailability driving users toward Anthropic — bears directly on the case's adoption-resolves hypothesis.
• 2026-09-29T20:53:11Z
  evidence attached: reddit.post.1wthevd — Concrete pricing/eligibility detail — Dots gated behind a ~$100/month plan and unavailable even to Pro subscribers — that materially shapes the adoption hypothesis.
• 2026-09-29T20:53:11Z
  evidence attached: reddit.post.1wthmjk — High-engagement launch-week evidence that Dots excludes EEA/UK/Switzerland — a material constraint on the adoption trajectory the case resolves on.
• 2026-09-29T20:53:10Z
  evidence attached: reddit.post.1wtgt4r — shared external link with case evidence
• 2026-09-29T18:07:40Z
  grounded: converges/high — OpenAI productizing a screenless, voice-first home companion that personalizes to its owner is the most consequential party yet arriving where Scott's AI-as-int
• 2026-09-29T17:56:03Z
  case created — Two proposals are one DevDay episode — the announcement and the getting-started guide for the same product — consolidated into a single case anchored on OpenAI's own announcement with front-page traction.

Decision trace

• 10-11 10:03attention_routeThe editor compared this story and chose to keep watching.
• 10-11 08:31sensor_dirtycomment_update
• 10-11 04:43repriceReliability cluster gains a fifth independent breakage report (delegation/sub-chat feature broken after update) but each report remains uncorroborated; the Oct 29 carve-out expiry (~19 days out) remai
• 10-11 02:50attention_routeFirst comprehensive assessment since launch; Oct 29 terms deadline creates a natural decision point for Scott's LiteLLM routing and cost-tiered architecture.
• 10-11 02:42attention_candidateattach
• 10-11 02:42attachEarly adopter reports Dot's delegation/sub-chat feature broke after an update — real-world breakage evidence for the launched hardware.
• 10-11 02:36propose_attachEarly adopter reports Dot's delegation/sub-chat feature broke after an update — real-world breakage evidence for the launched hardware.
• 10-10 21:55repriceReliability cluster gains a fourth independent report (403 errors and browser crashes on the cloud computer) but each report remains uncorroborated; the Oct 29 carve-out expiry (~19 days out) remains
• 10-10 21:37attention_routeThe editor compared this story and chose to keep watching.
• 10-10 21:33attention_candidateattach
• 10-10 21:33attachUser-reported 403 errors and browser crashes on Dots cloud computer, relevant to launch-week adoption friction.
• 10-10 21:33propose_attachUser-reported 403 errors and browser crashes on Dots cloud computer, relevant to launch-week adoption friction.
• 10-10 11:34repriceNew power-user feedback (1x1sfy7) is too early (1 upvote, 7 comments, uncorroborated) to shift the case's meaning; the Oct 29 carve-out expiry (~2 weeks out) remains the binding clock. Measured h
• 10-10 07:07attention_routeThe editor compared this story and chose to keep watching.
• 10-10 06:58attention_candidateattach
• 10-10 06:58attachPower-user feedback on Dots hardware experience — material user evidence for the case tracking whether the device sustains adoption beyond launch novelty.
• 10-10 06:41propose_attachPower-user feedback on Dots hardware experience — material user evidence for the case tracking whether the device sustains adoption beyond launch novelty.
• 10-09 10:25attention_routeThe editor compared this story and chose to keep watching.
• 10-09 10:06attention_routeDense dated-receipt material across Scott's canon; Oct 29 terms clock makes it time-boxed. High relevance, low heat — briefing inclusion for the token-burn economics and cap mechanics.
• 10-09 08:02repriceA claimed 24-hour stress test (1x0qf1x) adds to the execution-model evidence pile but is too early (1 upvote, 0 comments, uncorroborated) to shift the case's meaning; the tail remains cold (0.17
• 10-09 04:55attention_routeDense dated-receipt material across Scott's canon; Oct 29 terms clock makes it time-boxed. High relevance, low heat — briefing inclusion for the token-burn economics and cap mechanics.
• 10-09 04:49attention_candidateattach
• 10-09 04:49attachA claimed 24-hour stress test is early hands-on evidence about how OpenAI Dots actually executes tasks, relevant to whether the new hardware surface proves durable and usable.
• 10-09 04:39propose_attachA claimed 24-hour stress test is early hands-on evidence about how OpenAI Dots actually executes tasks, relevant to whether the new hardware surface proves durable and usable.
• 10-08 18:04attention_routeThe editor compared this story and chose to keep watching.
• 10-08 15:29sensor_dirtycomment_update
• 10-08 11:04attention_routeThe substance changed materially since the Sep 30 launch note: the architecture teardown, the first quantified burn attestation, and curtailment already underway convert this from 'shipped produc
• 10-08 10:34repriceThe launch tail crossed the low-heat threshold the last reprice set: case rate ~1.3 pts/h against a 758 peak with no new participants, communities, or outlets — the token-burn post's residual upv
• 10-08 10:27attention_candidateattach
• 10-08 10:27attachLaunch-week reliability complaints (device answering once since launch, top comment claiming GPT-Live-1 API calls frequently fail) are direct evidence on whether the Dot sustains adoption.
• 10-08 10:25propose_attachLaunch-week reliability complaints (device answering once since launch, top comment claiming GPT-Live-1 API calls frequently fail) are direct evidence on whether the Dot sustains adoption.
• 10-08 01:22sensor_dirtycomment_update
• 10-07 21:22sensor_dirtyvelocity_spike
• 10-07 21:22sensor_dirtycomment_update
• 10-07 17:58repriceThird independent abuse-cap report (1wznf8g) plus a staff-sounding quote conceding 'virtually unlimited' is momentary — and an uncorroborated Pro-200 20x-to-10x halving line — shifts the cas
• 10-07 17:58groundOpenAI — the most consequential party available — shipped the consumer-scale version of Scott's Give-the-Agent-a-Workshop thesis, and the teardowns confirm his exact reading: the dot's '
• 10-07 17:29attachTop users hitting abuse-prevention cooldowns on a dot marketed as 'virtually unlimited' is material post-launch erosion of the device's core promise.
• 10-07 17:24propose_attachTop users hitting abuse-prevention cooldowns on a dot marketed as 'virtually unlimited' is material post-launch erosion of the device's core promise.
• 10-07 14:23sensor_dirtyvelocity_spike
• 10-07 06:24sensor_dirtyvelocity_spike