The argument in one line.
The June 15 billing change is a boundary enforcement, not a price hike — and every builder who's panicking is paying the price for skipping the audit step their tools were always asking them to do.
Read if. Skip if.
READ IF YOU ARE…
- You run automated Claude workflows — cron jobs, CI/CD triggers, background agents — and need to know if June 15 will break or cost you.
- You followed a 'hype channel' tutorial to build an AI operating system with named agents and a custom frontend, and you just realized it all runs on claude -p.
- You want a decision framework for where to move scheduled AI tasks: Cowork vs. Routines vs. do nothing.
- You're trying to understand the difference between claude -p and the Agent SDK and why Anthropic is billing them differently.
SKIP IF…
- You only use Claude interactively — in the desktop app or an IDE — and have no automated background tasks.
- You're already on the API with your own billing and this change doesn't touch you.
The full version, fast.
Starting June 15, claude -p (headless CLI) and the Agent SDK move out of your subscription and into a separate credit pool: $20 on Pro, $200 on Max. Interactive Claude in the IDE and desktop app is untouched. Before changing anything, audit what you're actually running using the Skills & MCP tab in your observability dashboard — if your automated tasks fall within those credit limits, you may not need to migrate at all. If they don't, the path is straightforward: move scheduled skills into Cowork Scheduled Tasks (local-device, free within the ecosystem) or Routines (cloud-hosted, rate-limited by plan tier). The hype-channel AI OS builders have the hardest road — every agent run is headless and now metered — but the skills themselves are portable; migrating them into Cowork is the recommended fix.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 01:43
01 · What changed and who it hits
Claude -p and Agent SDK defined via sketchnotes; distinction from interactive use clarified; hype-channel builders flagged as most exposed
01:43 – 02:47
02 · The new credit pool
The $20-$200 credit tiers explained; reframed as a boundary not a price hike; extra usage credits warned against
02:47 – 04:41
03 · Step 1 — measure before you panic
7-day audit of what's running, token cost, invocation frequency; observability dashboard walkthrough; Skills & MCP cost-per-run table
04:41 – 06:40
04 · Where to move it — Cowork and Routines
Cowork Scheduled Tasks as the free migration path for most users; Routines for cloud-hosted needs; decision based on always-on device and plan rate limits
06:40 – 09:11
05 · The bigger problem and the boring fix
Hype-channel AI OS rearchitecture requirements; Kairos as Anthropic's signal; endorsement of skills-based SOPs over elaborate frontends
Lines worth screenshotting.
- claude -p and the Agent SDK are the same engine under two different wrappers — a command and a library — now billed as a single separate category.
- The $20–$200 credit pool is a boundary drawn between interactive and headless use, not a price increase on what you were already doing.
- Cowork Scheduled Tasks run inside Anthropic's ecosystem and don't draw from the metered credit pool — they're the free migration path for most cron-job use cases.
- Routines are the cloud equivalent of Scheduled Tasks but are rate-limited by plan tier (roughly 5–15 simultaneous remote daily runs).
- Making decisions without measuring token usage first is the same mistake as building elaborate frontends without measuring whether anyone needed them.
- The 'AI employee with a clickable frontend' pattern was always fragile — any Anthropic policy change would break it, and here we are.
- Observability is the prerequisite to migration: you cannot responsibly move automated tasks until you know their cost per run and invocation frequency.
- Anthropic's roadmap (Kairos, always-on task agents) signals they intend to own the scheduled-agent layer — third-party wrappers around this will keep breaking.
- Reliability and determinism beat adaptability for business automation — an AI that does the same thing well every day is more valuable than one that improvises.
- Standard operating procedures turned into skills are more durable than custom agent architectures — they survive billing changes, model updates, and API restructures.
Measure your automation before the deadline moves it.
WHAT TO LEARN
The builders who will absorb this change cleanly are the ones who already knew what their automated tasks cost — the rest are paying the price for skipping the audit.
- claude -p and the Agent SDK are the same engine — knowing that means one billing change covers both, and one migration path fixes both.
- The $20–$200 credit pool is a boundary between interactive and headless use, not a price increase on what most users were already doing interactively.
- A 7-day audit of token cost and invocation frequency is the minimum prerequisite before deciding whether to migrate, rearchitect, or do nothing.
- Cowork Scheduled Tasks run inside Anthropic's ecosystem and are not billed against the metered credit pool — the migration path for most cron-job use cases is free.
- Routines add cloud hosting to the equation but come with rate limits (roughly 5–15 remote daily runs by plan tier) — only move there if you need the device-off guarantee.
- Elaborate custom frontends layered over headless Claude will always be vulnerable to platform changes — the more native the infrastructure, the fewer forced migrations.
- Turning standard operating procedures into individual skills is more durable than building agent systems — skills are portable across any scheduling infrastructure.
- Reliability and determinism are more valuable for business automation than adaptability — an AI that executes the same workflow correctly every day compounds faster than one that improvises.
Terms worth knowing.
- claude -p
- The headless mode of Claude Code that runs Claude as a background process — no interactive UI. Used in cron jobs, CI/CD pipelines, and scripts. Moving to metered billing June 15.
- Agent SDK
- Anthropic's library (importable into any app or script) that lets code call Claude programmatically. Same underlying engine as claude -p, just accessed differently. Also moving to metered billing June 15.
- Cowork Scheduled Tasks
- Claude Code's built-in cron-like scheduler. Tasks run inside Anthropic's ecosystem on your local machine — not billed as headless API calls. Requires an always-on device.
- Routines
- Cloud-hosted scheduled tasks that run on Anthropic's infrastructure, not your local machine. Rate-limited by plan (roughly 5–15 simultaneous remote daily runs depending on tier).
- Headless Claude
- Running Claude without a human-facing interface — silently in the background via cron, CI/CD, or SDK calls. The category now being moved to a separate credit pool.
- Kairos
- An always-on task management agent Anthropic has in development, referenced in leaked roadmap data. The creator cites it as evidence that Anthropic intends to own the scheduled-agent layer natively.
Things they pointed at.
Lines you could clip.
02:07
“A boundary, not a price hike.”
03:58
“Without doing any of this measuring upfront, we cannot possibly make a decision that is actually directed from data. It would just be on FOMO and hype and worry, and those are the worst types of things to make decisions on.”
08:30
“It's boring, but you will never run into problems like this as you would if you follow a hype-based custom approach that makes no business sense.”
08:10
“There is never gonna be an AI grader that can learn something without you, the human in the loop, deciding whether what it's actually outputting is good or not.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
analogystory
00:00So Anthropic recently announced more changes to their billing, more specifically around Claude minus p and the agent SDK. For those of you who have been building from the hype channels out there, this is gonna be a massive problem because it's gonna change the entire way that your AI operating system works. In this video, I'm gonna show you exactly why it's a problem, then I'm gonna show you how to fix this problem so that you don't run into it ever again.
00:20Let's get into it. So at the time of me filming this, everything that you're currently doing at Claude is inside your subscription. So your Claude minus p runs and anything you're doing with the agent SDK all neatly sits inside here.
00:29But like I said, from June 15, that's all gonna be different. For those of you who don't know, Claude minus p is essentially just running Claude headlessly for you. So if you've set things up with a cron job or running something silently in the background, that is using Claude minus p.
00:42The other side of this is the agent SDK where you would import this into any app that you're building or scripts so that you can use various aspects of the Claude SDK. Both of these will now be moving to a new billing model. In terms of headless Claude, I imagine this will affect pretty much anyone who's been using Claude in an IDE or for some form of software development as well as those, like I said, who have been building crazy apps around this trying to integrate Hermes into Claude and building all of those task based apps that you see on YouTube at the moment.
01:07But then more importantly, if you have built an AI operating system based on any of the hype channels out there, you're gonna be into a much larger problem because they build those elaborate front end systems where they have named agents that run away and build things for you, and everything is clickable on a front end prototype.
01:22In another video that I made previously, I said everyone is building their AIS wrong specifically for that reason. If Anthropic ever made a change, that entire system would break, and here we are two weeks later. So for those of you who are just running a few cron jobs and a few other things, that's much simpler to solve.
01:37But But for those of you who unfortunately went and built your entire business around this, you're gonna have to do some much heavy lifting to get things going. So in a nutshell, the changes are not gonna change anything you do in your interactive parts of using Claude. So if you're using Claude in the IDE or in the desktop app, none of that stuff is gonna be changing.
01:51This is specifically for Claude minus p and for the agent SDK, and you're gonna be getting a new credit system over here depending on the plan that you're on. If you're on the pro plan, you're gonna get $20, and that obviously scales accordingly to your max plan over here ending on $200. And this is built entirely on the API rate.
02:06So this credit just goes towards that API. Once you've hit that, obviously, it will stop unless you've got extra usage credits enabled, but I wouldn't really wanna do that because this costs way more than it actually needs to compared to running it inside your subscription.
02:19So there's a different path that we need to take to fix all of this. So the first thing that I want you to do is not to panic. You just need to figure out what it is that you've currently got running, how it's running, and then measure that over a period of seven days to see how many tokens you're using, how often the skill needs to run, what sort of data it's bringing back, and what systems it's actually going into.
02:35You should already have a map of this considering you went and built the thing. But if you did install one of those plug and play things from a more hype channel, you might have to take a more ground up approach, which you can do by watching my videos at the bottom of the screen over here. It'll show you exactly how to set this thing up from scratch the proper way.
02:51In terms of measuring how many tokens you're using and figuring out a whole bunch of other things inside your environment, I definitely recommend setting up observability. So I have an entire video, again, that I'll link below. It will set all of this up for you, including this pretty dashboard so that you can see what skills are running in your environment, how long they run, and a whole bunch of other stuff related to context and security.
03:08All I'm doing here is reading the logs that are stored locally on my computer, so I'm not running any of that Claude minus p stuff within this unless we get down to this task board over here. But even when I filmed this video, I said people shouldn't be using this mission control task board because it's just unnecessarily wasting tokens.
03:22But back to the video, the whole point here is to measure exactly what is running. So if we had to go over to our activity or our skills tab, we would be able to see the cost per runs that we've had over the last thirty days based on the models that we've been using.
03:35So you can see my most hungry skill over here is the Sketchnote Illustrator, which is the one I used to draw these pretty slides for the videos that I put out there. The idea here though is that you want to track your token usage for your skills, because like I said, we still get some money from Anthropic. They're gonna give us between 20 and $200.
03:49So the important part here for measuring is understanding what runs, how often it runs, and how much it costs. Because based off of that, that depends on the actions that we're gonna take. So if you already have one of these elaborate systems and it turns out that you're actually within those credit limits, probably don't need to change anything.
04:04I still recommend that you would build it differently because, again, that is entirely elaborate and not necessary at all. But if you just had some cron jobs as well, you might fall inside this whole token limit thing. But without doing any of this measuring upfront, we cannot possibly make a decision that is actually directed from data.
04:18It would just be on FOMO and hype and worry, and those are the worst types of things to make decisions on. The other thing that we can measure under our skills and MCP tab over here is we can see how many times a skill was invoked, and that's really important as well. Like I said, it's gonna tie into how we're actually gonna be running this thing, because now that Cron is gonna start charging us and various other things are gonna start charging us, we obviously need to and should have already been using Anthropic's native functionality inside Claude Cowork.
04:43That's why they built it, and it works pretty damn well. So we've now measured everything, and we built somewhat of an audit of our environment. We understand exactly what skills are running, when they're running, and how much they cost.
04:52Now we need to decide if we actually need to move these things. If their cost and the amount of times that they run are within that billing credit that Anthropic is gonna give us, we probably don't need to do anything. If they're not, then we need to sort them into various categories that we understand the different methods that we can use to have them scheduled or to have our work running.
05:08So your first option is to use co work schedule tasks. We can just come on over here. You can create it with Claude if you need a copilot to help you do it, or you can set it up manually.
05:15And then this is pretty much just a cron job, but because it's running inside Anthropic's ecosystem, you're not gonna be charged as if you're outside running Claude minus p on a headless mode as you would if you were running it inside your IDE, which is where I run most of my stuff. Again, because I've got the $200 and the things that were scheduled inside here, they were so minor, I don't actually need to move them.
05:33But for some of the bigger things like lead gen, which only runs once a week, it does consume a lot of tokens, that will add up despite the fact that I have $200. So the simplest thing for me to do is to literally just chuck it in here in exactly the same way that I had it running before. There's not much more to change beyond that.
05:48Another option that you will have is routines. I'm not gonna go into those in-depth. I have an entire video that breaks this down step by step.
05:53I'll link that as well below. But this is the exact same thing. It just runs in Anthropix Cloud, so you have the benefit of their infrastructure taking care of this for you.
06:00You don't need to have your device always on as you would if you were running a co work scheduled task because this thing is currently running locally. They don't have any cloud functionality for this. So if you don't have a device that's always on, I would then recommend moving to routines.
06:13Something to note on routines though, depending on the size of your plan, again, you're gonna have rate limits on that. I think it's between five up to 15. That will probably change as the product matures as well.
06:22Again, that that is why it is so important to start with these first two steps over here because when you have the actual data, you know where things can go. Without that, you're just gonna be guessing, and you might be using a routine when you absolutely do not need one. So I would base my decisions on whether I've had this always on device and whether I need that cloud functionality.
06:37And then from that, I would just make my decision on where to put those automated skills. But for those of you who have a much larger problem, let's say you have one of these task board things with an AI as an employee that's doing all of the stuff in the background that probably really wasn't working in the first place, you're gonna have to rearchitect this entire thing because every single run that this agent does, it's gonna be running off of Claude minus p.
06:56This is all headless. It's all outside of Anthropic's infrastructure. It's not the end of the world because your skills and all of that stuff, it's obviously universal.
07:03You can just pop them straight into co work, and that's exactly what I recommend that you're doing. So if you are in that situation, watch the videos that I put down below about how to build an AI operating system, and it will walk you through setting things up inside here step by step with probably the exact same functionality that you've been using, and there's elaborate front ends from the other channels, but it will be way more robust, and you will never run into this problem again, specifically because Anthropic is moving towards having AI as an employee.
07:27We've seen they're bringing out Kairos, which is gonna be their always on task management agent. We just don't know when it's coming in. It was in the leaked data from a few months ago.
07:34So the signals have always been there, and that's why I've stepped away from making these really pretty front ends and things like that on this channel. Because I knew as soon as Anthropic said they weren't gonna allow third party people, OpenAI then followed and didn't even give anyone credits to run things in headless mode.
07:48You just have to pay for the API automatically, it was very clear that they're trying to lock everyone into the ecosystem. So if that doesn't sit well with you, then obviously you can go and use OpenClaw and you run an open source model or something like that.
07:59But really, Cowork is a great product, even Codex is starting to turn out to be a great product, So you're not gonna end up on the wrong path as long as you stick to the best practices that you should be doing, because in business, you want reliability, determinism, and you wanna make sure that it's just doing the same thing that you're doing every day.
08:13For instance, if you have a business that is making sales, you don't need an AI employee to adapt on the fly and stuff like that. You just need to keep doing whatever you're doing and refine the skill over time alongside the agent because there is never gonna be an AI grader that can learn something without you, the human in the loop, deciding whether what it's actually outputting is good or not.
08:31The TLDR here is that you already know what should make your business successful. So if you've taken your standard operating procedures on how you get leads, on how you deliver success to clients, all you're doing is turning them into skills. So get really good at making skills and then just schedule them.
08:45Set them up inside co work or code, and have them stay in a robust infrastructure and build it that way. It's boring, but you will never run into problems like this as you would if you follow a hype based custom approach that makes no business sense.
08:57I hope this short video was helpful. If you have any more comments, leave them down below. I will help you get through this if you need that.
09:02Otherwise, check out the videos on the screen now. They'll definitely help you on your journey, or you can check out my community where we are helping business leaders achieve success with AI every single day. Thanks very much for watch
The Hook
The bait, then the rug-pull.
On June 15, Anthropic draws a line between interactive and headless Claude — and for anyone running background agents, cron jobs, or SDK-powered scripts, the rules just changed. This is the nine-minute audit and migration guide for the builders who want data before decisions.
Named ideas worth stealing.
02:47list
Measure → Sort → Route
- Measure (7-day audit: what runs, how often, token cost)
- Sort (within credit limits vs. over limits)
- Route (do nothing / Cowork Scheduled Tasks / Routines / rearchitect)
Three-step framework for responding to the billing change without FOMO-driven overreaction
Steal forAny migration decision involving automated AI tasks or cost-threshold pivots
08:30concept
SOPs into Skills
Convert standard operating procedures (lead gen, client delivery) directly into Claude skills, then schedule them — avoids elaborate frontend abstractions that break on platform changes
Steal forAI automation consulting, workflow productization, training SOPs
How they asked for the click.
VERBAL ASK
08:55next-video
“Check out the videos on the screen now. They'll definitely help you on your journey, or you can check out my community where we are helping business leaders achieve success with AI every single day.”
Verbal CTA with implied end-screen cards. Community link (Skool) mentioned but not shown on screen. Low friction — no pitch, just pointer to related content.
MENTIONED ON CAMERA
FROM THE DESCRIPTION
PRIMARY CTAWhere the creator wants you to go next.
Visual structure at a glance.
