CHAPTERS
What launched at “Code with Claude” and why it matters
Claire recaps attending Anthropic’s first developer event and previews five practical updates across Claude Code and Claude Managed Agents. She frames the video as a fast tour of what shipped, how it works, and what she’d build with it.
Claude Code Routines: scheduled or event-driven automations
The first major update is “Routines” in the Claude Code app—automations you can trigger on a schedule or via webhooks. Claire highlights this as a long-awaited feature for turning repeated manual workflows into dependable background jobs.
Building a weekly changelog-based newsletter routine
Claire walks through creating a routine that reads a project changelog and drafts a customer-facing newsletter every Monday morning. She explains the prompt constraints to keep the content focused on customer value rather than internal work.
Routines + connectors: Slack/GitHub integrations and team workflows
She expands the routine idea with connectors and team-oriented triggers. The point is that routines can be invoked by other systems and can post results where teams already work.
Managed Agents “Outcomes”: rubric-based self-iteration until done
Next, Claire introduces “Outcomes” in Claude Managed Agents, similar to Codex’s /goal concept. You define what “done” means via a rubric, and the agent self-grades and iterates until it meets the target.
Concrete Outcomes use case: shipping a “ship-ready PRD”
She makes Outcomes tangible by describing PRD creation cycles that typically require repeated feedback and alignment. With a rubric, an agent could iteratively improve a PRD until it matches a “ship-ready” standard.
Multi-agent teams in Managed Agents: orchestrator + delegates
Claire highlights a new multi-agent framework where you can programmatically define a team of agents working in the same container/file system. It supports an explicit hierarchy and per-agent toolsets.
Example multi-agent setup for PRDs: strategy, critic, and implementation review
She proposes how a PRD product could benefit from specialized agent roles. The orchestrator coordinates while sub-agents provide distinct perspectives (product strategy, critique, technical review).
Dreams: on-demand consolidation of agent memory across sessions
The “Dreams” feature focuses on agent memory—writing helpful markdown artifacts to disk so future sessions perform better. Dreams provides an explicit API primitive to review many sessions and synthesize what should be remembered.
Research preview and the bigger idea: memory (and forgetting) as primitives
Claire notes Dreams is in research preview and not broadly accessible yet, but it signals how labs are productizing agent memory. She also raises the complementary need for “forgetting” and purging stale or harmful memories.
Usage and rate limit increases: more time, fewer peak-hour constraints
The final announcement is practical: higher Claude Code usage limits and improved rate limits. Claire emphasizes this as the change many users will feel immediately day-to-day.
Wrap-up: the five takeaways and what they signal about Anthropic’s strategy
Claire quickly reiterates the five launches and why they’re useful now: automation (Routines), goal-converging agents (Outcomes), coordinated teams (multi-agent), improved memory workflows (Dreams), and higher limits. She closes by positioning Anthropic as aiming to be a leading agent platform for builders.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome