--- title: "The Rise of the Stateful Agent" type: post url: "https://robotpaper.ai/the-rise-of-the-stateful-agent/" canonical: "https://robotpaper.ai/the-rise-of-the-stateful-agent/" markdown_url: "https://robotpaper.ai/the-rise-of-the-stateful-agent.md" published: "2026-04-03T21:38:00.000+00:00" updated: "2026-10-22T21:57:57.000+00:00" tags: ["Pattern", "openclaw"] author: "Roy Osherove" author_links: ["https://robotpaper.ai", "https://x.com/royosherove", "https://www.linkedin.com/in/osherove/", "https://forms.gle/jQSx5KoXvrVA1JCK7", "https://robotpaper.ai/about-roy.md"] description: "OpenClaw kicked off a new pattern: the stateful agent. Persistence, long-term state, proactivity and tools in one loop. Why it matters and where it's going." usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original post)." license: "https://creativecommons.org/licenses/by/4.0/" --- # The Rise of the Stateful Agent It's hard to believe [OpenClaw](https://github.com/openclaw/openclaw) (read "ClawdBot") was released only about 4.5 months ago. Nov 24 Openclaw was released on Github publicly. It's been making history ever since. I'll treat it only from a tech standpoint, but it *is* a phenomena. OpenClaw start a new type of pattern that did not exist before. Commonly called [Stateful Agent — Pattern Definition (with Conversation Log)](https://robotpaper.ai/pattern-stateful-agent/) - it's really a few things in one that make it a killer product: - **Persistence**: Before OpenClaw agents were mostly built to be "stateless" between sessions. But OpenClaw tries to remember and stay in the same session continuously. - State: Keeping long term state, including handling state compaction , short and long term memory mechanisms, as well as semantic local search, but defaulting to file based search. - Session (gateway): with a long running single session "main" that you can connect to from anywhere - **Connectivity**: The Gateway is able to be a global connector from both web and social tools like Whatsapp, Telegram and more. You can start a session on your computer, and continue on your phone. - **Autonomy**: Proactive event based scheduler allows the agent to have both a 30 minute heartbeat that "does stuff" , and ability to schedule cron events that trigger other "stuff. - **Identity**: OpenClaw created its own "Soul" and "User" file and created the illusion of identity for itself and the user. - **Ease** of **configuration**: Everything is done via markdown files, so the agent can change itself very easily. Each of these features on its own presents some sort of advancement in how agents can work, and combined, these have created an emerging wave, a renaissance if you will, of personal assistants around the world. The ability to talk with the agent from anywhere, that it "knows" you and what you worked on together a week or two ago, that it can command a machine and do what you allow it to do without being bound by traditional agent rules opened a lot of eyes to the reality that agents can also be "unconstrained". ## Double Edged Swords This double edged sword of ability to do anything by default, presented itself quickly when non-technical users installed openclaw on their local machine and opened the openclaw gateway to the internet, allowing without realizing it, multiple types of security issues to happen and compromise their machines. This does not detract from the value of the technology, and in the right hands it can become very powerful as well as secure. ## Current uses Today OpenClaw is being used mostly as a personal assistant for many people. In enterprise situations companies are still searching for a path forward. - Many companies now offer quick VPS hosting for your openclaw instance, AWS included with LightSail OpenClaw. - Many companies are trying to get their employees to use OpenClaw as part of the job - this is still mostly unsolved, but [some solutions](https://github.com/aws-samples/sample-OpenClaw-on-AWS-with-Bedrock?tab=readme-ov-file) are starting to appear for the various enterprise problems that come up in such situations governance, compliance, Permissions Policies, Data Isolation, Monitoring, Dashboards, Instance Vending, User Management and more. ## Future Uses - Read-Write Full Stack Agents: I believe that the next wave will be of [full stack builder agents](https://github.com/inceptionstack/loki-agent/) - OpenClaw, Hermes and friends will be used not only as a Personal Assistant, but as a stateful full-stack builder agent, able to close the full cycle of coding-deploy, monitor, fix without humans in the loop (mostly). - Read-Only Steward Agents: Readonly agents will reside in every piece of any company, as monitoring, alerting and general discussion agents. every part of every system will have its own knowledge base and realtime state that has a "steward" agent responsible for helping with that part of the system and that people can work with. --- ## About the author **Roy Osherove** - Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: [https://x.com/royosherove](https://x.com/royosherove) - LinkedIn: [https://www.linkedin.com/in/osherove/](https://www.linkedin.com/in/osherove/) ### Contact - Contact form: [https://forms.gle/jQSx5KoXvrVA1JCK7](https://forms.gle/jQSx5KoXvrVA1JCK7) ### License Content on robotpaper.ai is licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/): reuse, quote and adapt with attribution (Roy Osherove, link to the original post). More about Roy and his other sites and projects: [https://robotpaper.ai/about-roy.md](https://robotpaper.ai/about-roy.md)