| ▲ | puglr 7 hours ago |
| It's a bit disheartening that this is generating so little discussion (this thread seems to be the one with the most comments, currently at 8). 99% of my max plan usage is non-interactive, and this post-June 15 pricing will far, far exceed what I can afford. I assume this applies to a great deal of us. |
|
| ▲ | solenoid0937 6 hours ago | parent | next [-] |
| It's not bad at all. You get $200 in monthly extra usage credits. Unless you are a deeply unprofitable user this change is no big deal. |
| |
| ▲ | brianwawok 6 hours ago | parent | next [-] | | The $200 plan is easily providing $2000 of AI usage. So with this change your bill goes from $200 to $200 + $2000 -$200 = $2000. That’s a 10x jump. Stuff like gas town is dead in the water | |
| ▲ | sigseg1v 6 hours ago | parent | prev | next [-] | | is using a Ralph loop for all tasks with "claude -p" and using my weekly limit up to 100% considered some kind of unprofitable outlier? It's a command line tool, it would be ridiculous to expect that a large number of users don't do this. I never launch "claude" interactively by itself. My understanding is that now with this workflow I will pay the same amount but get much less usage before getting to 100% for the week. How is that not bad? | | |
| ▲ | BoorishBears 4 hours ago | parent [-] | | They've probably (rightfully) identified long horizon autonomous development isn't quite there yet, so most stuff created by forcing Claude to run until you hit 100% of your weekly limits is going to be relatively low value slop that will not convert to long-term sticky spend/usage vs someone actively steering Claude until they hit their limit. If anything you might be an outlier if you do this and are actually producing something of reasonable value down the line. They know if the value provided by subsidized usage is too low, they're literally burning dollars for nothing: people won't feel any great pain losing it one day and definitely won't convert. |
| |
| ▲ | gcr 6 hours ago | parent | prev [-] | | [dead] |
|
|
| ▲ | mkw5053 7 hours ago | parent | prev | next [-] |
| Out of curiosity, how are you using it and for what? |
| |
| ▲ | puglr 6 hours ago | parent [-] | | Lots and lots of automation, along with long-running multi-instance headless tasks. My usage, which I was on the verge of increasing via a second Max plan, would cost 3 figures per day, rather than per month. I already know this because my initial tooling was prototyped against direct API usage, and that was the cost of my usage patterns. That is not sustainable for me. I understand that Anthropic can't subsidize all of us forever, but this will force me away from claude which is unfortunate. A number of the people I work with are similarly affected. | | |
| ▲ | DonsDiscountGas 3 hours ago | parent | next [-] | | I'm curious what you're doing so often and repeatedly that can't be done with more normal software. Or maybe write a good school, I've noticed Haiku+good instructions often matches Opus | |
| ▲ | 5 hours ago | parent | prev [-] | | [deleted] |
|
|
|
| ▲ | paulddraper 7 hours ago | parent | prev [-] |
| Yeah, it's a pretty wild change. It's one thing for Anthropic to ban subscription usage of OpenCode etc of their backend. It's another thing to use their tools and still not get the full usage. Claude's recent one 9 of uptime [1] might have something to do with it. [1] https://status.claude.com/ |