131–140 of 185 posts
Earlier quoted context omitted.
That's a CO2 emissions leader board!
That’s almost no CO2 emissions at all. Here is a CO2 emissions leaderboard (need to sort by the correct column): https://celebrityprivatejettracker.com/leaderboard/
Earlier quoted context omitted.
It’s a true statement - no weekly limits, just a daily limit. Easier to work with when you can only get locked out of your tool for 23h59m
You're going to send 1,000 messages in 1 minute?
2k tokens/second is insane. While I'm very much against vibe coding, such performance essentially means you can get near-github copilot level speed with drastically better quality. For in-editor use that's game changing.
At full pace that means 62 mins until you hit the daily cap.
Earlier quoted context omitted.
Ironically, that's how I got the whole idea of symbol-level edits. I was working on project like that, and realized that a lot of work is actually fairly small edits. But to do one right, you need to you need to look through a bunch of classes, abstraction layers, and similar implementations, and then keep in your head how to get an instance of X from a pointer to Y, etc. Very annoying repetitive work. I tried copy-p…
Totally agree with your view on the symbolic context injection. Is this how things are done with code/dev AI right now? Like if you consider the state of the art.
> running at speeds of up to 2,000 tokens per second, with a 131k-token context window, no proprietary IDE lock-in, and no weekly limits! I was excited, then I read this: > Send up to 1,000 messages per day—enough for 3–4 hours of uninterrupted vibe coding. I don't mind paying for services I use. But it's hard to take this seriously when the first paragraph claim is contradicting the fine prints.
To put this into perspective, github copilot Business license is 300 "premium" requests a MONTH.
Earlier quoted context omitted.
I don't see what's hard to understand about this.. other providers have weekly limits and daily limits. If you max out your daily every day you might still hit your weekly after 3-4 days of usage, meaning you cannot send more for the rest of the week. This is saying that no such weekly limit exists on top of the daily. E.g. see https://techcrunch.com/2025/07/28/anthropic-unveils-new-rate...
Claude Code does not have a daily limit, it has 5 hour windows that reset. On the $100 plan it's pretty hard to hit a window limit w/ Sonnet unless you're using multiple/subagents. The $200 is better suited to those who do that or want to use a significant amount of Opus. Also the weekly limit selling point is silly - it almost certainly only impacts those who are abusing, ie. running 24/7.
How do Claude's rate limits actually work?
I'm not a Pro/Max5/Max20 subscriber, only light API usage for Anthropic - so it's likely that I don't really understand the limits there.
For example, community reports that Anthropic's message limit for Max 5 translates to roughly 88k token per 5-hour window (there's variance, but it's somewhere in this 80-120k ballpark based on system load; also assuming Sonnet, not Opus). A normal user probably won't consume more than 250k token per day with this subscription. That's like 5M token for a month of 20 active days - which doesn't justify the 100 USD subscription cost. This also doesn't square with Anthropic's statement that users can consume 10000+ USD of usage on the Max 20 tier.
I'm clearly misunderstanding Claude's rate limits here. Can someone enlighten me? Is the 5-hour window somehow per task/instance and not per account?
> running at speeds of up to 2,000 tokens per second, with a 131k-token context window, no proprietary IDE lock-in, and no weekly limits! I was excited, then I read this: > Send up to 1,000 messages per day—enough for 3–4 hours of uninterrupted vibe coding. I don't mind paying for services I use. But it's hard to take this seriously when the first paragraph claim is contradicting the fine prints.
Tried this out with Cline using my own API key (Cerebras is also available as a provider for Qwen3 Coder via via openrouter here: https://openrouter.ai/qwen/qwen3-coder ) and realized that without caching, this becomes very expensive very quickly. Specifically, after each new tool call, you're sending the entire previous message history as input tokens - which are priced at $2/1M via the API just like output tokens.…
The API price is not a reason to reject the subscription price.