Always-on agent
Also known as: persistent agent, 24/7 agent, cloud-resident agent, asynchronous agent
The shift from reactive chatbot to always-on agent is one of the defining moves of 2026. A reactive assistant waits for you to open a chat window and type something. An always-on agent runs on a server somewhere, watching for conditions you defined, taking pre-authorized actions, and surfacing results when they matter. Products like Gemini Spark, Claude Cowork, and ChatGPT Agent all operate on some version of this model.
The technical requirements are meaningfully different from a standard chat loop. Always-on agents need persistent state storage (so the agent remembers what it already did), event-driven triggers (something that wakes it up when a condition changes, like a new email arriving), scheduled execution (running a task every Monday morning), and robust error recovery (because a lot can go wrong in a long-running background process). Builders working at this layer are effectively designing mini operating systems for autonomous work.
The practical implications for trust and control are significant. An agent that can send emails, book meetings, and execute code on your behalf while you sleep is genuinely powerful. Good implementations check in before irreversible actions. The design pattern that's emerging: wide autonomy on read and research tasks, explicit human approval on write and send actions. Google calls this 'asynchronous agency,' the idea that you delegate intent rather than micromanage each step.