29:07How I AI · Tutorial
Loop engineering for beginners
A plain-English field guide to every loop type — heartbeat, cron, hook, and goal — with two live builds in Claude Code and Codex.
June 17thThe argument in one line.
Anthropic shipped five practical agent-building features at Code with Claude—routines, outcomes, multi-agent orchestration, Dreams memory, and doubled usage limits—that make it easier to build, schedule, and refine autonomous workflows in production.
Read if. Skip if.
READ IF YOU ARE…
- A developer or technical founder building with Claude's API or Code app who wants to understand what shipped at Anthropic's first developer event and how to use it.
- A product manager or technical leader evaluating Claude's capabilities against competitors and needs a concrete breakdown of five new features with live demos.
- Someone already using Claude Code who's wondering what changed in the last few weeks and wants a 12-minute overview instead of reading release notes.
SKIP IF…
- You primarily use Claude through the web interface and have no plans to build with the API, Claude Code app, or managed agents — most of these features are developer-focused.
- You're looking for deep technical documentation on implementation or API specs — this is a product announcement recap, not a how-to-build guide.
The full version, fast.
Anthropic's first developer event shipped five practical upgrades that push Claude Code from a chat-style coding assistant toward an agent platform you can schedule, grade, and stack. The core mechanism is a new set of primitives: Routines fire Claude Code jobs on a cron, GitHub webhook, or generic HTTP trigger, locally or in the cloud; Outcomes lets a managed agent self-grade against a markdown rubric and iterate up to twenty times until done; multi-agent orchestration defines an orchestrator plus up to twenty-five sub-agents with their own toolsets against one filesystem; and Dreams consolidates past sessions into written memories on demand. Five-hour usage limits doubled across Pro, Max, Team, and enterprise seats, so you can actually use it.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 00:23
01 · Cold open
Claire frames the video: she attended Code with Claude, will walk through five things in under ten minutes.
00:23 – 00:58
02 · Promise of five things
Sets the scope: what they are, how they work, what she'd build with each. Promises to keep it under ten minutes.
00:58 – 02:38
03 · Routines — live demo
Walks through the new Routines surface in the Claude Code app. Clicks New routine, names it Weekly newsletter, points it at changelog.md, sets Mondays at 6AM, picks a folder. Compares the feature to OpenCLAW crons.
02:38 – 03:29
04 · Routines — three trigger types
Slide breakdown: cron, HTTP webhook, GitHub webhook. Connectors (Slack, GitHub) come along. Runs local or in the cloud. Example use case: weekly PRD audit posted to team channel.
03:29 – 05:33
05 · Outcomes — rubric-graded agents
Anthropic's answer to OpenAI Codex 'slash goal'. Define what done looks like via a markdown rubric, the agent self-grades and iterates up to 20 times. Walks through a ChatPRD example: a rubric-graded 'Ship-ready PRD' mode.
05:33 – 06:59
06 · Multi-agent — coordinator + delegates
API lets you define a multi-agent team that shares one container and file system, up to 25 concurrent. Explicit orchestrator and sub-agent hierarchy, per-agent toolsets. Example: a PRD orchestrator with strategy, critic, and eng-review sub-agents working in parallel.
06:59 – 09:22
07 · Dreams — agent memory primitive
Memory framed as just writing markdown to disk. Most harnesses do it on a session-close hook. Dreams is different — it's an explicit API call to take N past sessions, review them, and surface what to commit to long-term memory. In research preview; she doesn't have access yet. Side-note about wanting a 'forgetting' counterpart.
09:22 – 10:00
08 · Usage limits doubled
Five-hour limits doubled across Pro, Max, Team, and seat-based Enterprise. Peak hours going away for Pro and Max. Opus API rate limits going up.
10:00 – 11:08
09 · Recap + SpaceX aside
Other stuff she didn't cover (data centers in space, SpaceX partnership). Re-summarizes the five practical takeaways. Lands on: none of it was mind-blowing, but it's all practical, and Anthropic is positioning as the agent platform of choice.
11:08 – 11:38
10 · Outro + show CTA
Bye + standard pod outro: like, subscribe, comment, find on Apple Podcasts / Spotify, see all episodes at howiaipod.com.
Lines worth screenshotting.
- Claude Code's Routines feature lets you trigger agent tasks on a cron, webhook, or GitHub event — without writing any infrastructure code.
- Outcomes let you define what done looks like as a markdown rubric, then the agent iterates up to 20 times until it satisfies the grading criteria.
- A 25-agent multi-agent framework with an orchestrator and explicit sub-agent hierarchy is now callable via a single API — no custom orchestration code required.
- Dreams is a memory primitive: you call it against a list of past sessions and it decides what to commit to long-term agent memory, the same way sleep consolidates human memory.
- Agent forgetting is as important as agent memory — nobody is building the purge equivalent yet, but they will need to.
- Peak usage hours are being removed for Claude Pro and Max plans, ending the most frustrating friction point for serious builders.
- Scheduling a weekly newsletter draft from a changelog.md is a routine that took one configuration form and zero code — something that previously required a cron job and custom prompting infrastructure.
- A strategy agent, a critic agent, and a technical review agent all working in parallel on the same file system is now a native primitive, not a custom build.
- Rubric-graded outcomes shift agent performance from 'did it complete?' to 'did it meet the success criteria?' — a fundamentally different quality bar.
- Anthropic's positioning is becoming clearer: they want to be the agent platform of choice for builders, not just the model provider underneath other platforms.
Steal the format.
Five-things-in-ten-minutes playbook
A confident, calm 'I was there, here's what shipped' field report beats a hype reel every time — especially for changelog-style content.
- Set the contract in the first 30 seconds: number of items + time cap. 'Five things, under ten minutes' is a promise the viewer can hold you to — and is the reason they don't bounce.
- Use a split-screen frame: bold slide on the left, your face PiP on the right. Costs nothing in shoot time, doubles the perceived production value, and lets you read code on screen without looking like a screen-share.
- Per item, hit the same three beats: what it is, how it works, what you'd build with it. Repetition is the format — viewers feel the rhythm and stay.
- Pair every abstract primitive with one concrete demo. She tied Routines to a weekly-newsletter cron she actually built on camera. Outcomes got a 'ship-ready PRD' example. The viewer always has somewhere to land.
- End on a hot-take, not a recap. 'None of this was mind-blowing, but it's all practical' lands a thesis viewers can repeat — way stickier than 'so those were the five things'.
- Don't oversell what you don't have access to. She flagged Dreams as research-preview and admitted she hasn't touched it. That credibility carries the rest of the video.
Terms worth knowing.
- Claude Routines
- A Claude Code feature that lets users schedule automated agent tasks to run on a cron schedule, via HTTP webhook, or triggered by a GitHub event — without manually starting the session each time.
- Cron job
- A scheduled task in software that runs automatically at specified times or intervals (e.g., every Monday at 6am), commonly used to automate recurring processes.
- Rubric-graded outcomes
- A Claude evaluation method where the AI is given a scoring rubric and assesses its own output quality against defined criteria, enabling automated quality checks without human review.
- Claude Managed Agents
- Anthropic's API-level framework for building and orchestrating multi-agent pipelines, where Claude models can spawn sub-agents, delegate tasks, and coordinate work programmatically.
- Dreams (memory primitive)
- A research-preview memory feature in Claude that allows agents to consolidate and store important information from past sessions for long-term recall across separate runs.
- Webhook
- An HTTP callback — a URL that receives an automated notification when a specific event occurs in another system, used to trigger workflows between connected services.
- GitHub webhook
- A webhook configured in a GitHub repository that fires when specific events happen — like a push or pull request — enabling automated workflows to start in response to code changes.
- Tech debt
- Accumulated shortcuts, workarounds, or deferred improvements in a codebase that increase future development cost, typically invisible to end users but meaningful to engineering teams.
- Multi-agent framework
- A software architecture where multiple AI agents work in parallel or in sequence — each handling a specific role — coordinated by an orchestrating system to complete complex tasks.
- Usage limits (Claude)
- Caps on the number of messages or tokens a user can send to Claude within a rolling time period, enforced by subscription tier to manage compute costs.
Things they pointed at.
00:26eventCode with Claude (Anthropic's first developer event)
01:12productRoutines (Claude Code)
01:17toolOpenCLAW (Open Claude)
01:10productChatPRD
03:35productClaude Managed Agents (Claude API)
03:35productOpenAI Codex 'slash goal'
03:42productOutcomes (Claude API)
05:27productMulti-agent framework (Claude API)
07:03productDreams (research preview)
09:24productClaude Code Pro/Max/Team/Enterprise usage limits
09:56productSpaceX partnership / data centers in space
Lines you could clip.
05:05
“Define a rubric, give the agent the task, let it bang its head against that at least 20 times till it gets it right.”
08:26
“I think we think a lot about agent memory, but not a lot about agent forgetting.”
08:15
“This is what we do when we dream. We go through our day, we review it silently, and then we decide what to commit to memory.”
11:10
“None of this was mind blowing, but I think it's all really practical.”
11:18
“Anthropic is trying to be the agent platform of choice for builders.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphoranalogystory
Welcome back to How I AI. I'm Claire Vaux, product leader and AI obsessive here on a mission to help you build better with these new tools. Today, I attended Code with Claude, Anthropic's first developer event, and they announced some things in Claude code and Claude managed agents I think you wanna know about.
I'm gonna walk you through five things that launched today, how they work, what they are, and what I might build with them. We're gonna keep it under ten minutes, and this gonna be a quick preview of what you'll see in your new Claude code and Claude API products experience.
K. The first thing that shipped at code with Claude that I think you wanna know about are some updates to the Claude code app. And one of the updates that I know we've all been waiting for is routines, the ability to trigger events or actions on a schedule.
We love it. You know I love OpenCLAW, and what I love about OpenCLAW are the crons. And so now ClawdCode has that built in right here in the app.
All you have to do is click new routine. You can either run it locally or remote. I'm gonna run it locally, and I'm gonna say weekly newsletter.
This is something that I haven't been doing. I'm sorry. If you're a ChatPurity customer, I know I haven't done my newsletter.
I'm gonna say, look at our change log and draft a newsletter for us to send weekly.
And then I'm gonna go in here and just say, we have a changelog.md in the docs folder.
Review it every Monday and write a customer facing newsletter based on the best customer facing features we shipped.
Don't talk about behind the scenes things like tech debt or security unless they really impress customers.
Okay. So I'm gonna do that. I'm gonna run it daily or no.
Sorry. I'm gonna run it weekly on Mondays at 6AM, and I think that's all I need to do.
Oh, I'm gonna select my folder, um, where my project is, and then I'm gonna create create. And now Cloud Code will run my newsletter draft cron every week, and then I can come back in here, grab the HTML.
If I were being really fancy, I would hook this up to my newsletter platform. I would hook it up to my Slack and ping us. But, again, this is very useful to me.
This is something that I used to kick off manually in Claude Code every Monday, and now I can do that here in Claude Code on a schedule. So how does that work?
There are three trigger types. You can trigger them on a cron, which is a schedule, um, HTTP or a GitHub webhook.
So you can do sort of a normal webhook or a GitHub webfoot. You can trigger these three ways, scheduled, like I just did, off of a GitHub action or a general webhook.
So you can hook it up to other systems to kick off a routine. All the stuff in connectors come along. So I have Slack connected.
I have GitHub connected. So you can use those things as part of your routine, and it can run-in the cloud or it could run on your laptop like I showed.
And this is an example of a use case where you could say weekly, I want you to check every PRD modified this week and check if it matches our rubric and post a summary to the team channel.
So that's item one. The second one is in Cloud managed agents in the API. If you haven't paid attention, OpenAI released something in Codex called goal.
You can do slash goal in beta and Codex, and it'll basically , do what's called a Ralph loop against the problem until it actually hits the goal. Anthropic released something very similar in the Cloud API called outcomes. You define what done looks like for an agent.
It can self grade and iterate until it gets there. There's a couple interesting things you need to know about how outcomes are defined. They all anchor on what's called a .
So there's a markdown file that's uploaded either through the files API or in line, and it's gonna tell your agent what success looks like. Then there is a grader, and it can do up to 20 iterations on the task to get to the outcome that you're going for.
I wanna walk through this one in a very specific example to make this just a little bit more concrete for folks. So so imagine that I want you to ship a ship ready PRD. And I don't know if you can relate to this.
Often you go through feedback cycles. You have check it against priorities. You have to check it against technical capabilities.
Now using a quad managed agent, you could, in theory, write a rubric, which is what does a good ship ready, um, PRD look like. And then the agent can just take your PRD or your idea and iterate over and over and over again until it's fixed.
Of course, you could expect of course, you could expose this to your customers in an app like I might do for chat PRD. But, again, this idea of outcome is define a rubric, give the agent the task, let it till it gets it right.
I think this is really interesting model for agentic products and something I suspect many of us will use. The second thing I really love is a multi agent framework supported in Cloud managed agents. So now you can, through the API, explicitly define a multi agent team that's going to work against the same container, the same file system up to 25, which is kind of amazing.
You can have a a orchestrator and then delegates, and so there's explicit hierarchy. And each agent can have its own toolset. I think this is really cool because now you're able to define not just individual agents, but teams of agents programmatically through the API.
And so the example I would give for something like chat PRD is you could have a PRD orchestrator. This is sort of like the master agent that is intended to define and drive the work across the team. And then you can have three pieces or three sub agents, a strategy agent that reflects the CPO voice, the critic agent that's sort of, like, supposed to poke at the holes in the PRD.
I like being the critic agent. And then end review that can maybe have access to something like GitHub to optimize the technical implementation of the PRD.
And so you can define this as you see over here in the API. You define an agent in the API. You give it a orchestrator level set of tools, and then you can define the sub agents in the in the API with their own set of tools.
And then you could expose that, as you can see here on the right, as three agents all working in parallel against the same problem owned by the coordinator or level.
Again, I think this is an interesting enhancement on the primitives of agents that people are gonna be using quite a bit.
Okay. The next one I really like, it is . So this is all about agent memories.
Just to make it simple for folks, memory is basically the idea of writing markdown files to the file system your agent uses that helps it do a better job the next time. It's not that fancy. Often those files have a date on them, but you don't really have to overthink it.
But creating those memories is a little hard. And often a lot of the harnesses right now write memory on a hook. They write them on an event.
And so what they do is, like, when you close a session, it writes memory or when something happens, write memory. Or, like, with Open Claw, you can explicitly tell it to write memory. But what I like about Dreams, which is a very funny brand for an agentic memory product, but we'll allow it, is it's a primitive to call against a list of agent sessions.
So let's say you've done 50 things with your agent. It's an explicit call to take those 50 sessions, review them, and then come up with important memories to write to disc.
And as I'm saying this, I guess this is what we do when we dream. We go through our day. We review it silently, and then we decide what to commit to memory.
I don't know. I don't know if this is the perfect metaphor, but it's the one we got, and it looks great on a on a branded website. This one's in research preview, so I don't think everybody has access to this through API.
I certainly don't have access to it, so I'm looking forward to touching it. But why I think this one's important to know is it just gives you a frame of reference for how Anthropic and these labs are thinking about the primitives, again, of agents and agent memory.
And you can predict that some framework like this is going to be integrated into agentic platforms or agentic products where on some action or some review regular cadence, You're gonna review past sessions, and you're gonna explicitly write the right things to disc so they can be referred to moving forward.
Side note, I think we think a lot about agent memory, but not a lot about agent forgetting. So I'm looking forward to, like, the purge version of this, which is dreams that tell you what to forget.
I don't know if that's, like, trauma erasure or whatever, but I think there's something interesting here. Okay. And then number five, the only announcement people really care about, which is usage limits, are up.
So starting today, Claude Codes' five hour limits are now doubled across pro, max, team, and seat based enterprise platforms. Peak hours are going away for pro and max plans, and the rate limits for Opus models in the API are going up.
So we can all use these products more. Again, what do we see today at Code with Claude? Lots of other stuff.
They might put data centers in space. There was a partnership with SpaceX. All sorts of fun things are happening.
But the things that I think you can use immediately, routines for scheduling tasks in Claude code so you can get things done either on a webhook or on a schedule, which is the ability to set a rubric and task and have an agent work against that task at least 20 times to nail the rubric, multi agent orchestration, which allows you in the API to define an orchestrator role and sub agents, I think up to 25, to get work done from different points of view with different tools, dreams, which are a way to consolidate agent memory over sessions over time and do that on demand.
And then finally, we can all use more Cloud Code, which makes everyone happy. I do not know if these limit increases apply to Cloud Design.
I suspect they do not, but I hope they will. I think they launched a lot of stuff that we can use practically right now in Cloud Code and gave me some good ideas for what the future of AgenTic products look like.
None of this was mind blowing, but I think it's all really practical. And it just gives you the idea that Anthropic is trying to be the agent platform of choice for builders. I look forward to seeing what you build with it, and I'm gonna go play with the API.
Bye. Thanks so much for watching. If you enjoyed the show, please like and subscribe here on YouTube or even better, leave us a comment with your thoughts.
You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app.
Please consider leaving us a rating and review which will help others find the show. You can see all our episodes and learn more about the show at howiaipod.com. See you next time.
The Hook
The bait, then the rug-pull.
Claire Vaux opens cold from her studio: she just got back from Code with Claude — Anthropic's first developer event — and has five things to show you in under ten minutes. No drama, no hype reel; she just sits down and starts naming what shipped, what's research preview, and what she'd actually build with each. The title screams power-up, but the video is closer to a calm field report from someone who reads changelogs for fun.
Named ideas worth stealing.
02:36list
Three trigger types for Routines
- cron (schedule)
- HTTP webhook
- GitHub webhook
Routines in Claude Code can be fired three ways and run either locally on your laptop or in the cloud, with connectors (Slack, GitHub) attached.
Steal forJoe's daily/weekly automations across MCN, JoeFlow, Clip Lab — schedule Claude Code to do the things he currently kicks off manually every Monday.
03:42model
Outcomes loop (Anthropic's Ralph-loop equivalent)
- markdown rubric
- grader
- up to 20 iterations
- result: satisfied | needs_revision | max_reached
Anchor an agent on a rubric, let a grader judge each iteration against that rubric, loop up to 20 times until the agent self-grades as satisfied. Anthropic's flavor of OpenAI Codex's slash-goal feature.
Steal forAny place Joe has a quality bar he can write down — sales-page copy reviews, JSON runsheet validation in Mod Producer, sermon/script polishing. Write the rubric once, let the agent iterate.
05:35model
Coordinator + delegates pattern
- one orchestrator agent
- up to 25 sub-agents
- shared filesystem/container
- per-agent toolset
Programmatic multi-agent team where one master agent drives work and sub-agents each have their own tools but share state. Demo: PRD orchestrator with strategy, critic, and eng-review sub-agents.
Steal forJoe's Paperclip lineup (JACE, REESE, SAGE, RYDER) — formalize them as an orchestrator-plus-delegates team through this primitive instead of one-prompt monoliths.
07:03concept
Dreams memory loop
- take N past sessions
- review them asynchronously
- surface important memories
- write to disk
An explicit primitive to consolidate agent memory on demand rather than on every session-close hook. Async, runs up to 100 sessions per dream, watchable in real time.
Steal forJoe's MCN agents — instead of writing memory on every hook, run a Dream over the last week of conversations and let the model decide what was actually worth remembering.
How they asked for the click.
VERBAL ASK
11:18subscribe
“If you enjoyed the show, please like and subscribe here on YouTube or even better, leave us a comment with your thoughts. You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app.”
Soft, post-roll, after she's already said 'Bye' to camera. Standard podcast outro pattern — no hard pitch, just menu of where else to find the show. Mentions howiaipod.com at the very end.
MENTIONED ON CAMERA
FROM THE DESCRIPTION
PRIMARY CTAWhere the creator wants you to go next.
OTHER LINKSAlso linked in the description.
Visual structure at a glance.
