Post #3768237

I've been using Fable today and really getting things done. I actually asked Claude what I can do to keep costs down, Here are the basics. 1. For Fable, current prices are $50 per 1 million tokens, this is like 750000 words, it's a lot. I worked on a task that built like six features and spend 172000 tokens, about $10 or so ($8 actually). Read tokens, when Claude reads files, does things with input, are $10 for 1 million tokens. What kills you /. me is cached read/write, the thing that happens when you keep a long session going and it has to read the whole conversation over and over again as your context gets longer. That cost is $1 per million reads (I had 16.7 million in this session and 10.50 out, I had less out caching. But the basic idea is that I would havce spent like $35 on today's feature fest, mostly because of freaking cached reads/writes. 2. Start a new detailed build feature in eitehr a new session or compact so you don't have as much cached read or write. 3. use tools that are appropriate for the task at hand. If Opus can handle it, give it to Opus. I spent most of the day doing map data queries and efficiencies, something that doesn't spend as much. Also, who knows, as with Opus, 4.7 was and still is way more expensive/not as aefficient, I expect Fable to continue to get more efficient. It is what it is, by 11:59 PM eastern, being able to use usage credits to use Fable will go away, it'll be up to you, the user, to learn how to lessen your costs if you're gonna spend to ust it.