# Anthropic — Building always-on agents

- Company: Anthropic (anthropic.com)
- Announced: 2026-11-13
- Category: not stated
- Coverage: 1 outlet
- Announcement: no
- Group: covered
- Source: https://claude.com/resources/articles/building-always-on-agents
- Record: https://forck.live/items/36037-building-always-on-agents
- Subject: Claude
- Models affected: Opus 5.5, Opus 5

Anthropic's guide explains the architecture behind always-on agents, which stay stateful across sessions and act without direct supervision, and says recent model advances have made them practical to run. The company attributes the resurgence to better judgment in the latest models, which it says are more reliable at reading user intent and knowing when to check in, and to falling intelligence costs. On one long-horizon coding benchmark, Anthropic says Opus 5.5 cost 78% less per solved task than Opus 5, against 40% less on typical workloads. The guide describes five primitives: an event inbox, timers, memory, permissions and an outbox, and notes customers have asked how to add the experience to their own products. It walks through the run cycle, in which an agent sleeps, wakes on an event, works inside a session and saves what happened before sleeping again. The inbox is recommended as the source of truth with one active worker at a time, while timers live in a separate store and are fired by a scheduler that polls for due follow-ups and schedules.

## Evidence

Verbatim from https://claude.com/resources/articles/building-always-on-agents:

> Over the past few months, we’ve seen a resurgence of always-on agents.
> 
> Always-on agents are stateful and proactive, meaning they manage context across sessions and take actions without direct supervision. Underneath, they run on the same core loop as other agents. The difference is the surrounding architecture, which is built from primitives that control when the agents wake up, what carries over between runs, and how their work reaches the user.
> 
> The resurgence is largely due to recent model advancements, which have made always-on agents more practical to run. First, the latest models have better judgment: they’re more reliable at understanding user intent and knowing when to check in. Second, intelligence is becoming cheaper, with long-horizon tasks benefiting the most. For example, on one long-horizon coding benchmark , Opus 5.5 cost 78% less per solved task than Opus 5, compared with 40% less on typical workloads.
> 
> Customers have started to ask us how to integrate this type of experience into their own products. Some companies want to make their existing agents more proactive, while others are looking to build them from the ground up.

## Around this story

Outlets this record can name and link:

- Extrapolator — Anthropic publishes architecture guide for stateful always-on agents: https://extrapolator.ai/2026/11/14/anthropic-publishes-architecture-guide-for-stateful-always-on-agents

---

Record: https://forck.live/items/36037-building-always-on-agents
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
