# My nightly Claude Code cron was about to start costing real money > Source: > Published: 2026-06-14 15:01:36+00:00 A billing change lands tomorrow, and last week I went looking for what it would break in my own setup. Its headline is narrow. interactive subscription work stays exactly as it was, but anything running headless, in the background, on a schedule, starts drawing from a separate metered pool with its own limit. My subscription was safe. my habits were not. Somewhere along the way I had built the thing everyone builds. a nightly job that wakes up, calls the model to do some work, and goes back to sleep. Quiet, useful, and as of tomorrow, billed against a pool I never wanted it touching. **Two ways my work talked to Claude.** When I actually looked, every call I made fell into one of two buckets. First, there was me, sitting there, working live. asking, building, iterating. That is what the subscription covers, and it stayed put. Second, there was automation. scheduled jobs, background runs, anything that called the model with nobody in the loop. I had treated both as "using Claude", one undifferentiated thing. That billing change drew a hard line between them that I had never bothered to draw myself. **One of them was about to get metered.** Interactive work was fine. Automated work was the exposure. That nightly cron had felt free, because it rode the same subscription I was already paying for. Tomorrow it stops being free and starts metering against a separate quota. Same job, same output, suddenly a line item. Multiply one quiet background call by every night of a month, and the free automation I had forgotten I was running becomes a bill I never planned for. **Why the nightly cron was the casualty.** That broken pattern was specific. a headless call to the model, fired by a schedule, with nobody watching. It was also the shape I had reached for without thinking, because backgrounding a task feels like the smart, hands-off move. That change turned my cleverest-feeling automation into my most expensive one. **How I actually split it.** I did not kill the automation. I cut it in two. Work that needs no model, the gathering, the checking, the prep, stays in a plain scheduled script that costs nothing. Work that genuinely needs Claude moved back to where I am present and the subscription covers it. That schedule still runs. it stops calling the model behind my back. Unglamorous, and the whole fix. background does the cheap deterministic work, model work happens in the lane that was always covered. **My honest opinion.** Here it is. tomorrow's split raised no costs for me. it surfaced which of my automations were never on the subscription to begin with. I had blurred two different things into one word and let a metered pattern hide inside a flat-rate habit. That change created nothing new. it switched on a light that showed what was already there. Anyone running scheduled model calls on a subscription plan has the same light about to come on. **What the split actually exposed.** Nothing about my work got worse. one pattern got a price tag, and that price tag was honest. What I gained is knowing, for every automation I run, which side of the line it sits on. metered or covered, background or present, deterministic or model. I should have known that before a billing change forced me to look. now I cannot unsee it, and every new automation gets sorted on day one. If you run anything that calls a model on a schedule, go find it before tomorrow does. Whatever feels free is the thing most likely to surprise you. What background job are you running that you have never checked the bill for. I work through this in public, the wins and the freezes both, mostly on LinkedIn and YouTube. If the real version of building in the open is useful to you, that is where it lives. [LinkedIn](https://www.linkedin.com/in/mirzajhanzaib/), YouTube and X under Mirza Iqbal, and the work at [next8n.com](https://next8n.com).