The feature nobody covered this week just turned your AI memory system into an autonomous agent + the guide to wire it up

Anthropic shipped a feature earlier this month called /loop. It’s a command inside Claude Code that lets an agent run a task on a schedule, every five minutes, every hour, every morning at 9am, without you sitting there prompting it. The coverage so far has been about developer convenience. Automated monitoring and background polling.

That framing misses what actually happened. And not just because Claude Code isn’t only for developers anymore. Anthropic has said as much, I’ve said as much, and the user base moved past that assumption months ago even if the coverage hasn’t. Marketers are in Claude Code now. Product managers. Anyone willing to type in a terminal window, because it turns out a terminal is just a chatbot without the guardrails.

The real story is that /loop is the last Lego brick. If you’ve been following the agent conversation, you know there’s a short list of primitives an agent needs before it stops being a chatbot and starts being something you can actually delegate to. Memory. Proactivity. Tools. We solved memory a few weeks ago with Open Brain. Tools have been here through MCP. What was missing was the heartbeat, a way for the agent to wake up on its own and do work without you being the one to poke it every time. /loop is that heartbeat. And if you’ve already built Open Brain and connected it to tools, you’re now holding all the pieces.

That combination is, functionally, an OpenClaw you control.

Here’s what’s inside:

• The three Lego bricks and what happens when you stack them. I’ll add one primitive at a time so you can see exactly what changes at each layer, from a parrot that repeats advice to a detective that builds a case.

• Use cases from energy tracking to sales pipelines. Specific examples of how memory plus proactivity plus tools creates compound value that no single pass can match.

• Why this is the OpenClaw stack without the chaos. Same core capability, none of the security nightmare. And why the architectural separation between scheduling and memory is what makes it durable.

• The morning briefing where every primitive fires at once. The capstone use case that shows what genuine delegation looks like when the agent has been working overnight.

• What’s still missing, and why the terminal is time travel. Honest gaps, and the argument for why using Claude Code right now puts you months ahead of everyone waiting for the friendly UI.

• Prompts and two companion guides to build it yourself this weekend. A step-by-step walkthrough to set up the /life-engine skill with Claude Code, MCP, Telegram, and /loop — plus a second guide that turns those briefings into short animated videos on your phone.

Let me show you what I mean by adding one brick at a time.