In Claude Code, run /model and select Fable from the model picker, or switch directly with:
/model claude-fable-5
In the API, switch the model ID parameter to "claude-fable-5" in both the Messages API and Claude Managed Agents. For some accounts, an admin may need to enable access first.
The /claude-api skill in Claude Code can help you build with Fable on the API.
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.
You can also set "/effort ultracode", a new effort level that runs at xhigh and lets Claude decide on its own when a task warrants a dynamic workflow.
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 greatly improved the responsiveness of Claude while working. Thinking & tool calls are streamed and we’ve fixed a number of bugs that might have made it look like Claude was hanging while it was just thinking for a long period of time.
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
We've been using the plugin extensively at Anthropic.
Across our internal rollout and benchmarks, we’ve seen a 30-40% decrease in security-related comments on PRs opened using the plugin.
The plugin serves as a lightweight first pass, catching issues before a full code review
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.
How it works: Claim the monthly credit once, and programmatic usage will draw from it automatically. When it runs out, you can keep going with usage credits (billed at API rates you turn on/off). If usage credits are turned off, usage pauses until the credit resets.
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
2/ Agent loop
• Sub-agent summaries now hit the prompt cache
• Opt-in 1-hour prompt caching is now honored correctly
• Parallel shell calls keep running if a read-only sibling fails
• 1M-context sessions use their full window before hitting "Prompt is too long"