๐๐น๐ฎ๐๐ฑ๐ฒ ๐๐๐๐ผ๐บ๐ฎ๐๐ถ๐ผ๐ป ๐๐ต๐ฎ๐ป๐ด๐ฒ๐: ๐ ๐๐ต๐ฒ๐ฐ๐ธ๐น๐ถ๐๐ ๐๐ผ ๐๐๐ผ๐ถ๐ฑ ๐ฆ๐๐ฟ๐ฝ๐ฟ๐ถ๐๐ฒ ๐๐ต๐ฎ๐ฟ๐ด๐ฒ๐
Claude is changing how it handles automation starting June 15, 2026.
Your monthly subscription fee is not increasing. However, how your usage counts is changing. Anthropic is splitting usage into two separate pools.
- Conversational Use: Chatting with Claude on web, desktop, or mobile. This stays in your flat-rate subscription.
- Programmatic Use: Running Claude via code or scripts. This now moves to a metered system.
If you only chat with Claude, nothing changes for you. If you run automation, you must act to avoid extra costs or broken workflows.
๐๐ผ๐ ๐๐ผ ๐๐ต๐ฒ๐ฐ๐ธ ๐ฌ๐ผ๐๐ฟ ๐จ๐๐ฎ๐ด๐ฒ
Follow these steps to see if you are affected:
โข Identify non-interactive use: Are you running claude -p in scripts? Are you using the Claude Agent SDK in Python or TypeScript? Are you using Claude Code in GitHub Actions? If yes, you are in scope. โข Check third-party tools: Do you use external apps that connect to your Claude account via the Agent SDK? These now count toward your new credit. โข Verify authentication: If your automation uses a Claude Platform API key, it is not affected. This change only impacts automation using subscription authentication.
๐ช๐ต๐ฎ๐ ๐ฌ๐ผ๐ ๐ก๐ฒ๐ฒ๐ฑ ๐๐ผ ๐๐ผ
Eligible plans will receive a monthly credit equal to your plan fee. You must claim this credit via an email from Anthropic.
Once you claim the credit, you have two choices for when it runs out:
- Enable Extra Usage: Your automation keeps running but bills you at standard API rates. Use this for production workflows that cannot stop.
- Disable Extra Usage: Your automation stops the moment the credit hits zero. Use this to set a strict spending limit for experiments.
๐ง๐ต๐ฒ ๐๐ผ๐ป๐ด-๐ง๐ฒ๐ฟ๐บ ๐ฆ๐๐ฟ๐ฎ๐๐ฒ๐ด๐
Automation is no longer a hidden cost inside a flat-rate plan. You must now design your workflows with cost in mind.
- Use Subscription Credits for: Personal helpers, light experiments, and individual tasks.
- Use API Keys for: Production systems, team-wide automation, and workflows that require clear, scalable billing.
Separating conversation from automation makes sense. Humans type slowly, which limits cost. Code runs fast, which can quickly consume resources. This split ensures you only pay for the speed of your code.
Optional learning community: https://t.me/GyaanSetuAi