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.
Monthly credit amounts vary by plan:
Pro: $20
Max 5x: $100
Max 20x: $200
Team Standard: $20/seat
Team Premium: $100/seat
Enterprise: Varies by seat type
After you claim the credit, it resets with each billing cycle. Credits do not rollover.
This means that third-party tools built on the Agent SDK like Conductor and OpenClaw work with your Claude plan, but will draw from your credit the same way your own scripts do.
There’s nothing you need to do today. Users will get an email on June 8 to claim their credits, and this change goes into effect on June 15.
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"
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.
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).
Running "/claude-api managed-agents-onboard" in Claude Code helps you configure a Claude Managed Agent for your use case, and gives Claude Code the context it needs to monitor and debug it afterward.