OpenClaw, Anthropic, and Gemma 4 just redefined what "agent framework" means. You need to pick a side.

In April, OpenClaw stopped being an agent harness and started being a runtime.

A month ago, the easy descriptions still fit. Chatbot wrapper, Claude launcher, viral terminal toy. By the end of April, none of them held. OpenClaw became an action layer for agents — a place where tasks, tools, memory, channels, permissions, subagents, and model choices come together into durable workflows. The model is no longer the product. The runtime is.

That shift matters because the model layer underneath it became more contested at exactly the same time. Anthropic pulled subscription-backed third-party usage back toward its own products. OpenAI moved the other way, opening ChatGPT and Codex subscription usage to OpenClaw users. Google shipped Gemma 4, built explicitly for agentic and on-device work. Local models got good enough for more background tasks. Claude is still valuable, but increasingly as a metered premium component rather than the default flat-rate engine for everything.

The mistake is to let the runtime fight swallow the product story.

A month ago, the builder ambition was to make an agent do something useful. Now it is to build a durable workflow once and swap the model underneath it. That is a much bigger idea, and it changes the builder opportunity completely.

Here’s what’s inside:

• Why April was the threshold month. TaskFlows, channels, memory, and routing all matured at once, and the combination is what crossed the runtime line.

• The Anthropic move, in context. What changed, why it was rational, why the developer community reacted the way it did, and what it tells you about the next twelve months.

• The seven workflows you can now actually build. Repo operations, code review memory, incident response, customer feedback, meetings to execution, model-aware routing, and team memory across agents.

• Why memory has to live outside the model. If the brain is swappable, memory cannot live inside any one brain — and that has implications for how you architect anything you build on top of OpenClaw.

• The Open Brain Agent Memory launch. A live ClawHub skill, a plugin package, and four recipes — code review memory, TaskFlow work logs, the OpenClaw Agent Memory recipe, and a Safe Agent Memory contract that draws the line between evidence and instruction.

The labs will keep fighting over the brain. The interesting question is what builders should do while they fight.