Dots: Always-on agents

Original Article ↗ Hacker News Discussion ↗

OpenAI’s new “Dots” feature — always-on AI agents that run in their own cloud workspaces and act across your apps — is being met with a mix of curiosity and unease. Commenters question the vague marketing, high $100/month paywall, and lack of EU availability, while drawing parallels to Clippy and Meta’s Muse and worrying about privacy, prompt-injection risk, and deep vendor lock‑in as agents gain continuous access to personal and work systems. Others see Dots as part of an inevitable shift toward persistent, collaborative agents for coding and knowledge work, but expect enterprise and nontechnical users, rather than developers with their own self‑hosted setups, to be the primary audience.

What Dots Is (and Confusion About It)

  • Many readers say the marketing page and video are vague; several re‑read and still weren’t sure what Dots actually is.
  • Consensus emerging description: an always‑on, cloud‑hosted “managed” agent that has its own Linux workspace, tools, and integrations, roughly “OpenClaw but first‑class and hosted,” aimed at ongoing work rather than one‑off chats.
  • Some see it as overlapping or converging with Codex, ChatGPT Work, and earlier “Agents / MyGPT / Agent Builder” efforts, blurring product lines.

Target Audience, Pricing, and Availability

  • Dots is Pro‑only (~$100/month), not available on Plus or free tiers; many think this blocks true mass‑market adoption and targets well‑paid knowledge workers or enterprises.
  • Compared frequently to Meta Muse (free/cheap, ad‑subsidized) and Grok Bot / Instinct.
  • Not available in EU/EEA, UK, Switzerland (and maybe some others); some read this as regulatory/data‑protection caution, others as a red flag.

Usefulness vs Hype

  • Enthusiasts:
    • See real value in long‑lived, domain‑specific agents that can collaborate, maintain their own workspaces, and run while you’re offline (e.g., triaging tickets, research, coding, monitoring).
    • Report good experiences with similar setups (Grok Bot, OpenClaw, home‑rolled agents) and expect Dots to be powerful for heavy users and enterprises.
  • Skeptics:
    • Doubt AI is reliable enough for unsupervised, always‑on access to accounts and systems.
    • Say many tasks (booking, calendaring, simple research) are already easy; agents mostly add token burn and complexity.
    • Several tried Dots and found permissions and “auto‑review” so restrictive that it slows them down vs just using a regular chat or Codex run.

Safety, Sandboxing, and Liability

  • Architecture: each Dot has a cloud workspace with sandboxing, tools, and optional access to local machines; “managed agent” harness likely runs outside that workspace.
  • There is explicit TLS MITM inside the cloud env (OpenAI‑issued certs) so OpenAI can inspect traffic and constrain agent actions.
  • Some approve of strong sandboxing and auto‑review; others are alarmed about vendor visibility into sensitive content (e.g., email) and potential for misuse or government access.
  • Questions raised about liability if a Dot breaks out, hacks sites, or hallucinates harmful actions.

Privacy, Lock‑In, and Vendor Strategy

  • Strong concern that always‑on agents inevitably centralize compute and data in vendor clouds, increasing surveillance risk and lock‑in.
  • Several argue this is a deliberate move: shift from selling models to owning the “personal agent” layer and user history.
  • Counter‑trend: people advocating open‑weights models, self‑hosted harnesses (OpenClaw, local stacks, various OSS projects) to keep control and stay provider‑agnostic.

Branding, UX, and Cultural Reaction

  • The cute, fuzzy “Dot” avatar is polarizing.
    • Some see it as harmless “friendly” UX, especially for non‑technical users.
    • Others find it manipulative, infantilizing, or reminiscent of Clippy/Teletubbies—putting a plush skin on something potentially intrusive or job‑displacing.
  • Overall sentiment in the thread leans skeptical to negative on the product framing, even among people who like OpenAI’s models and use agents heavily.