The writing of edits and code directly on my machine is something that happens on the client side. I don't see why that usage would be subject to anything but one-time billing or how it puts any strain on Anthropic's infrastructure.
> ... usage limits that would make it very difficult to use for Claude Code.
Genuinely interested: how's so?
Re:Claude Code Best Practices
by cypherpunks01 on Saturday April 19, 2025 @11:17AM
(#43736985)
Well, I think it'd be pretty irritating to see the message "3 messages remaining until 6PM" while you are in the middle of a complex coding task.
No, that's the whole point: predictability. It's definitely a trade off, but if we could save the work as is we could have the option to continue the iteration elsewhere, or even better, from that point on offer the option to fallback to the current API model.
A nice addition would be having something like /cost but to check where you are in regards to limits.
Re:Claude Code Best Practices
by unshavedyak on Saturday April 19, 2025 @12:37PM
(#43737499)
Conversely I have to manually do this and monitor the billing instead.
Claude Code uses the API interface and API pricing, and writes and edits code directly on your machine, this is a level past simply interacting with a separate chat bot. It seems a little disingenuous to say it's "hostile" to users, when the reality is yeah, you do pay a bit more for more reliable usage tier, for a task that requires it. It also shows you exactly how much it's spent at any point.