Engineering brief

Persistent AI agents are here. They need governance, not hype.

OpenAI3 min read · saves 51 min

At a glance

The brief is enough

Relevance
Practical value
Radar
Time horizon
This year
Warnings
  • High hype
  • Vendor pitch

OpenAI launched Dots — always-on agents that work across apps, fix bugs, and update decks. Impressive demo.

Persistent AI agents that work across your entire workflow are now a product, not a demo. Engineering leaders must decide how to govern them before teams adopt them ad-hoc.

Watch if you want to see the full demo flow and judge the latency/UX yourself before deciding whether to pilot Dots internally.

Summary

The new product. OpenAI announced "Dots" — persistent, always-on agents that work in the background, across multiple apps, and can be delegated complex multi-step tasks like migrating off a legacy API. A Dot watches your work patterns over time, surfaces urgent items before your day starts, and can even send text messages or take phone calls. It runs on the same Astra model and uses a cloud-based Codex harness, meaning tasks persist across devices.

Why now. OpenAI claims this is the product developers have been asking for most. The pitch is that earlier assistants (booking a flight) were trivial compared to what the technology can now do. The underlying model improvements — ChatGPT 6.1 sol (a cost-capability balance), UltraFast (300 tokens/second), and a new Decisions API for sub-second responses — make this kind of persistent, multi-step agentry technically feasible.

The trade-off. The demo is impressive — a Dot that updates your board deck, monitors bug reports, tests fixes, and handles wedding planning all at once — but it glosses over the messy operational realities. How do Dots handle conflicting instructions? What happens when two Dots step on each other in the same codebase? The demo showed a Dot catching a user testing issue and sending the designer to fix it, but said nothing about version control, rollback procedures, or human-in-the-loop approval gates.

What's missing. Security, compliance, and cost governance get a one-liner. OpenAI mentions "private tension" (zero-ETL privacy) and enterprise management through Microsoft tools, but there is no detail on audit trails, agent-to-agent authentication, or how to prevent a Dot from making costly API calls in a loop. The demos all show ideal conditions — the Dot finds the right Slack DM, the right PR, the right design file. Real enterprise environments have messy permissions, stale documentation, and 50 Slack channels no one remembers.

Hype check. The research intern claim is the weakest. Solving open math problems sounds transformative, but the video provides no citation, no peer review, and no detail on what "solved" means. The internal metrics (token usage up, model completes 33% of day-long research tasks) are self-reported with no external validation. The Dot demos are scripted and seamless — no loading spinners, no "I'll get back to you" delays. The hardware integration with robots feels like a teaser, not a product.

My take

I think Dots are the most consequential product OpenAI has announced since ChatGPT itself, not because the demos are perfect, but because the strategic bet is clear: turn ChatGPT into an operating system for work, with OpenAI as the platform beneath it. The governance gap is real, but it's also typical for platform shifts. Teams that run small, bounded experiments with Dots on low-risk workflows (monitoring, reporting, draft generation) will learn faster than teams that wait for the perfect guardrails. I am skeptical of the research intern claims, but I am not skeptical that persistent agents will change how software teams operate within two years. The right move is to assess, not adopt at scale.

What to do with this

  1. Pilot one Dot on a low-risk, bounded workflow (e.g., automated weekly status report generation) and measure time saved vs configuration overhead.
  2. Implement an agent governance playbook: define per-agent permissions, human approval gates for code changes, and cost tracking per Dot.
  3. Run a small internal hackathon with OpenAI's open-source Codex harness to understand failure modes before committing to a vendor-locked solution.

Watch the video

This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.

Related breakdowns

Get TL;DW

Too Long; Didn't Watch.

A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.

Free. Weekly. No hype.

Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.