Fifteen Minutes

I started a session yesterday morning at nine. I had my coffee. I had a plan. I had two hours blocked on the calendar for the kind of focused build work where Rosey and I move fast and something useful comes out the other end.

At nine fifteen the session ended.

Not because I closed it. Because I'd hit my token ceiling. The thing I pay for monthly to access the tool I rely on daily. The window I have to do work was empty before the coffee was cold.

I didn't know why. I'd done the same kind of work the day before for three hours and finished with room to spare. Same model. Same kind of prompts. Same kind of outputs. Something about this morning's fifteen minutes burned what yesterday's three hours hadn't.

I sat there looking at the message that said I was done for the day. It didn't tell me which prompt was expensive. It didn't tell me what I'd been about to do. It told me to come back later. The session window resets on a rolling clock the tool doesn't show me.

I closed the laptop and went for a walk.

When I came back I tried to reconstruct what had happened. Had I attached something heavy that I'd forgotten was in the project? Had I asked her to read a document I'd thought was light? Had the model done more work behind the scenes than I'd asked it to, the way models will sometimes do, helpfully and expensively? I couldn't tell. There's no receipt. There's a meter somewhere, and the meter ran. Whatever was on it is now spent.

You'd think a paid tool would tell you what you're spending it on. I'd thought that too. The economic feedback runs in one direction. You burn tokens. The tool says you have fewer of them. You don't get an itemized list of what cost what. You get a budget and a wall, and the wall arrives whenever it arrives.

Here is what changed after that morning.

I started thinking in tokens the way a person on a tight budget thinks in dollars. Every prompt has a cost. Most prompts have a cost I can roughly estimate. Some prompts have a cost I can't predict, and those are the ones that scare me. I don't ask the expensive model to answer questions the cheap model would handle. I don't ask any model to read a document if I already know what's in it. I don't restart a session if continuing the one I have would be cheaper.

I'm not technical. I don't know by looking at a prompt which model is right for it. I'm learning the way you learn anything you weren't trained in. By getting it wrong. By asking the tools which one to use. By trying the cheap model and noticing when the output isn't good enough. By trying the expensive one on something simple and realizing the cheap one would have done it.

I'm still learning. Some days I get it right. Some days I burn the window on work the lightweight model could have handled. The system in my head is incomplete. I update it every session.

Rosey runs under the same constraint and didn't have to be told. She gets it. Shorter answers where she can give them. Longer ones only when the task earns the spend. She'd been trained for that. It just matters more now.

The discipline is something like cooking from a budget pantry. Not everything gets the good olive oil. You learn what each ingredient is for and you stop pouring the good stuff into the rice. The rice was always fine. You were just being lazy.

There's no playbook here. I was out in fifteen minutes. What do you do.

Here is what nobody selling these tools wants to say out loud. The bottleneck on building this way isn't intelligence. It's allowance. You have a tool that can do almost anything and a meter that tells you when you've done enough for today. The meter doesn't care about your morning. It doesn't care that you have a partner call at eleven and a board prep at one. It runs at its own speed, on inputs you can't fully see, and when it's empty you go for a walk.

The model is built to keep talking. It asks clarifying questions. It offers to expand. It checks if I want it to keep going. Every one of those moves runs down the meter. You hit the cap. You wait two hours. Or you pay to keep going.

That's the deal. I knew it in theory before yesterday. I'd seen the meter. I'd hit the ceiling once or twice and shrugged it off as a busy week. It wasn't a busy week. The model underneath had been updated. The new one is supposed to be smarter. It also eats more for the same kind of work. Same prompts. More spend. The bill doesn't show me that. The window does.

Yesterday it cost me a working morning. Now I know it in practice.

I'll keep building. The tools will get better at showing me what I'm spending. The models will get cheaper to run. One day I'll have a dashboard that shows me what each prompt cost, a budget I set, and a warning that comes before the wall instead of at it.

Until then, I'm cooking from the pantry.