AI News Nuggets

Always-on agents make authorization a continuous control, not a prompt-time checkbox

OpenAI has introduced dots, persistent agents with their own cloud computer and connected tools, alongside documented safeguards for permissions, custom rules, action review, and safety monitoring.

Editorial read

This edition collects 1 notes across 1 topic areas and 1 source. Start with Persistent agents need explicit action boundaries and a review path that survives the move from one task to the next to get the week's main practical signal before scanning the remaining links.

Edition signal

The October 2 signal is that persistent agents require controls that remain meaningful after the original task has changed

OpenAI's dots are a product implementation, not a complete enterprise control model. Their persistent operation highlights a broader operating requirement: define what an agent may do autonomously, bind each connection to explicit permissions, keep high-impact actions reviewable, and preserve a way to stop, investigate, and adjust work as context changes. A long-running agent should not inherit a vague approval indefinitely simply because its first task was legitimate.

AgentsSecurityBusiness

Agents October 2 note

Official GPT-6 Astra system card and dots safeguards documentation

Persistent agents need explicit action boundaries and a review path that survives the move from one task to the next

Source: OpenAI

OpenAI has introduced dots: always-on agents powered by GPT-6 Astra that have their own cloud computer and browser, can use connected tools, and can continue work between conversations. OpenAI says users can set boundaries through permissions and Custom Rules; its safeguards include pre-action Auto-review and ongoing safety monitoring. Enterprise availability begins as an admin-enabled beta, initially off by default.

Why this matters: Treat persistence as an access-design change, not only a productivity feature. Before assigning ongoing work, define the allowed systems, data classes, recipients, financial or external effects, and escalation conditions. Make approval state and task scope visible to a reviewer, log material actions, and rehearse how to pause or revoke a connection. The useful test is whether a changed business context, a hostile message, or an ambiguous hand-off can cause the agent to act beyond its current authority.

Read OpenAI's dots safety and evaluation documentation