This piece is worth opening because it pulls the "always-on" headlines back to what the code actually says: "sampled again." The system prompt template OpenAI merged into its open-source repo in late August shows Persistent mode for what it is—no always-running process, no dedicated VM, just a loop that wakes every 1–3 minutes, checks state, acts if needed, and goes back to sleep. Before sleeping, the agent must record its goal, latest status, completion condition, and next check time, then decide what to do when it wakes.
I'd discount the hype a bit: this feature isn't live. The backend request still says "disabled," there's no billing system, and OpenAI says no near-term launch. The article gives two numbers that explain the hold—ProAgentBench shows models hit only 64.4% accuracy on judging when to proactively help, and Anthropic's engineering blog reports a 17% miss rate on real overreach during automated review. In a system that can self-wake every 1–3 minutes, a one-in-three timing error plus double-digit miss rate means incidents are a matter of frequency, not possibility.
Don't read this as "AI stands watch for you." A better take: it fits delivery-type tasks like CI, deployment, and builds—jobs that execute for one minute and wait for ten—shifting the mental burden of tracking from you to the model. It's a bad fit for open-ended work like proposals or designs that need human feedback; toss those in and you just get a scheduled nag bot.
What you can actually use today are three discipline rules from the template: write four-element checkpoints before sleeping, stay silent when nothing has changed, and prefer deterministic mechanisms like cron or webhooks for polling. These work right now, and they're more useful than waiting for the feature to ship.