A few patterns we frequently use with Fable 5:

Use Fable 5 as an "advisor."

An executor (Sonnet 5) calls Fable 5 for guidance.

Most tokens are billed at the lower executor rate. On SWE-bench Pro, Sonnet 5 + a Fable 5 advisor tool gets ~92% of Fable 5's score at ~63% of the price.

Fable 5 is called rarely (~once) per task to steer while Sonnet 5 executors the majority of the work.

See our docs to learn more:
platform.claude.com/docs/en/agents…

Claude Fable 5 is here. New model generation, new way of working.

Here's how to get started in Claude Code and on the Claude Platform: 🧵

https://twitter.com/claudeai/status/2064394146916229443

In Claude Code, run /model and select Fable from the model picker, or switch directly with:

/model claude-fable-5

New in Claude Code (research preview): dynamic workflows.

Claude writes an orchestration script on the fly, then spins up a large fleet of coordinated subagents in parallel to take on your most complex tasks.

Use the word "workflow" in a prompt to get started. Dynamic workflows are useful for tasks that are too big for a single agent loop, such as service-wide bug hunts, large migrations, or stress-testing a design.

They're powerful and can be expensive, consuming a lot of tokens fast. Start with a scoped task to get a feel for it.

We’ve been putting a lot of effort into making Claude Code more responsive & reliable.

Here’s an update on everything we’ve done: First for our new full-screen renderer (which should get rid of bugs like screen flickering), we’ve made a number of fixes for different environments and terminals.

You can turn it with the command: /tui feedback

We're working on making it the default in Claude Code soon.

We’ve shipped a security-guidance plugin for Claude Code that helps identify and fix vulnerabilities as you’re writing code.

Available for all Claude Code users. Install from the plugin marketplace (/plugins). It runs via hooks and reviews code on three levels:

- On file edits: looks for risky patterns like commonly misused dangerous libraries
- After model turns: reviews the full diff for harder-to-spot issues
- On commits: reads surrounding code to validate vulnerabilities

Starting June 15, paid Claude plans can claim a dedicated monthly credit for programmatic usage.

The credit covers usage of:
- Claude Agent SDK
- claude -p
- Claude Code GitHub Actions
- Third-party apps built on the Agent SDK We've heard your questions about SDK and claude -p usage sharing your subscription rate limits with Claude Code and chat.

Starting June 15, programmatic usage gets its own dedicated budget instead. Your subscription limits don't change, they're now reserved for interactive use.

Last week we shipped 50+ Claude Code reliability fixes. This week it's 60+ more.

Smoother long-running sessions, a more efficient agent loop, auth that works in more environments, and terminal fixes: 🧵 1/ Stability

• claude -p now handles >10MB of piped stdin
• Requests resume cleanly after waking a Mac from sleep
• Memory stays bounded when a stdio MCP server writes non-protocol data to stdout (was growing past 10GB)
• Output now appears reliably after thinking completes

In Claude Managed Agents, we’ve added multiagent orchestration, an outcomes loop for rubric-driven self-improvement, dreaming for self-learning, & webhooks. Multi-agent orchestration enables task delegation to specialized sub-agents.

Each sub-agent has its own context window, but they share a container + filesystem to coordinate work.

platform.claude.com/docs/en/manage…

Claude Code ships with a built-in skill for working with the Claude Platform.

Useful for model migrations, using API features (e.g., prompt caching), or onboarding to newer APIs like Claude Managed Agents. Running "/claude-api migrate" in Claude Code reviews your codebase and walks you through updating model names, prompts, and effort settings for a new Claude model (like Opus 4.7).