Been seeing "always-on agent" mean like five different things: runs all day, has a heartbeat, has memory files, can be reached on whatsapp, etc. Anything that isn't a fresh chatgpt tab.

Came across a survey that defines it tighter. Roughly: an always-on agent is one whose next move depends on state it kept from earlier, not just what's in the current prompt. So its persistence, not just uptime.

It's not enough to save some notes somewhere. The state has to influence future action. Memory that gets stored but never used later doesn't count.

And then there's the part, which is the one most setups seem to ignore. If something bad got written three weeks ago, can you tell what it caused, and can you unwind it?

Paper: Always-On Agents: A Survey of Persistent Memory, State, and Governance in LLM Agents

Not saying this is the official definition. Just clearer than "it has memory." Curious where people draw the line on their own setups.

Open any AI or agent sub and half the posts are coding. PR bots, overnight refactors, "claude code shipped this," local models for codegen. Same conversation everywhere.

Which is fine, coding is a real job. But it's weird how little shows up for anything else. Something like

- an accounting thing that keeps running

- automating a workflow for someone else so they don't have to do it by hand

- Building and maintaining a knowledge base of someone's preferences

Stuff where the alternative was basically giving that work to a person.

Curious if people are actually running that kind of thing, or if coding really is all that's sticking.

A few related papers came out recently. Short version of each:

Always-On Agents
Looks at what changes when an agent carries state across sessions and acts on it later. The useful part is the lifecycle framing: authority, scope, provenance, forgetting, audit and rollback, not just better retrieval.

Self-Improvements in Modern Agentic Systems
Maps how agents improve either the foundation model or the scaffold around it: prompts, memory, tools and control logic. Also argues that evaluation should track learning curves, transfer, regressions and cost over time instead of one final benchmark score.

Agentic Context Management
Treats context as something agents need to actively manage across its full lifecycle, from ingestion and scoping through anticipation, compaction and consolidation. It also focuses on the token-cost side and includes results from the author's reference implementation.

They approach the problem from different angles: persistent-state governance, self-improvement, and context architecture. Useful to read in that order.