441–450 of 695 posts
Hey all, Boris from the Claude Code team here. We've been investigating these reports, and a few of the top issues we've found are: 1. Prompt cache misses when using 1M token context window are expensive. Since Claude Code uses a 1 hour prompt cache window for the main agent, if you leave your computer for over an hour then continue a stale session, it's often a full cache miss. To improve this, we have shipped a few…
Earlier quoted context omitted.
https://www.reddit.com/r/Anthropic/comments/1s4iefu/update_o... is an official post by Anthropic. > Your weekly limits remain unchanged. During peak hours (weekdays, 5am–11am PT / 1pm–7pm GMT), you'll move through your 5-hour session limits faster than before. Overall weekly limits stay the same, just how they're distributed across the week is changing. I'm Eastern time and peak usage works out as 8am-2pm (the bulk o…
Yeah I hadn't been aware of that change previously. I'm also ET, but perhaps I just don't use it enough to hit the limits. They could definitely do to be more transparent, maybe instead of percentages, show a "credit" allocation such that the time-based variation in 5-hour windows is visible.
Earlier quoted context omitted.
We are taking it seriously, and are continuing to investigate. We are not trusting the metrics.
[flagged]
The way your tone and complaints come across reminds me of this. As a paying customer ($5k spend per month in my corporate job), I’d rather anthropic keep doing what they’re doing — innovating and shipping useful stuff at blinding speed — and not index on your feedback. I think the tradeoffs they would cost far outweigh the consequences.
Earlier quoted context omitted.
Sure, I really appreciate you looking at this. a6edd0d1-a9ed-4545-b237-cff00f5be090 / https://github.com/anthropics/claude-code/issues/47027 I'm happy to provide any other info that can be useful (as long as i'm not sharing any information about the code or tools we use into a public github issue).
Thanks for the report! This was fixed in v2.1.92. Please: 1. Upgrade to the latest: claude update (seems like you did this already) 2. Start a new conversations (resuming an old convo may trigger this bug again in that convo)
Earlier quoted context omitted.
Boris, you're seeing a ton of anecdotes here and Claude has done something that has affected a bunch of their most fervent users. Jeff Bezos famously said that if the anecdotes are contradicting the metrics, then the metrics are measuring the wrong things. I suggest you take the anecdotes here seriously and figure out where/why the metrics are wrong.
We are taking it seriously, and are continuing to investigate. We are not trusting the metrics.
Hey all, Boris from the Claude Code team here. We've been investigating these reports, and a few of the top issues we've found are: 1. Prompt cache misses when using 1M token context window are expensive. Since Claude Code uses a 1 hour prompt cache window for the main agent, if you leave your computer for over an hour then continue a stale session, it's often a full cache miss. To improve this, we have shipped a few…
> Since Claude Code uses a 1 hour prompt cache window for the main agent, if you leave your computer for over an hour then continue a stale session, it's often a full cache miss. To improve this, we have shipped a few UX improvements (eg. to nudge you to /clear before continuing a long stale session), and are investigating defaulting to 400k context instead I don’t understand this. I frequently have long breaks. I ne…
But my understanding is that we're talking about ~60GB of data per session, so it sounds unrealistic to do...
Earlier quoted context omitted.
Ah, so cache usage impacts rate limits. There goes the ”other harnesses aren’t utilizing the cache as efficiently” argument.
Claude Code is the most prompt cache-efficient harness, I think. The issue is more that the larger the context window, the higher the cost of a cache miss.
Earlier quoted context omitted.
Then you should offer to pay them for one. I’m sure they’d love to hear from you, and they could probably deliver one to you for the right price. But it will be a high price.
They don't offer a ZDR [0] for files, even if you have a BAA or dealing with HIPAA data, no matter how much you pay them. Trust me, we have tried. [0] https://code.claude.com/docs/en/zero-data-retention
Earlier quoted context omitted.
What right as a consumer do you have that is pertinent here, other than to have the vendor adhere to the terms of the agreement you have with them? Anthropic has many customers despite the fact that they have occasional problems. They’re not suing Anthropic because Anthropic isn’t promising in its agreement something they can’t deliver. I think you’re reading into the agreement something that isn’t there, and that’s…
I am not reading into an agreement, I am saying there is no agreement to be found to ensure service delivery and the associated liability that would come for any SLA. Also, where is the Anthorpic SLA for Enterprise? Does it exist? Just because people pay for things doesn't mean they know or understand what they are paying for. Nor is there the legal precedence to actually understand where the rub lies or how that imp…
I believe, respectfully, that’s precisely what is happening in this thread because you keep complaining about the absence of an SLA that was never in the agreement, as though it is—or is supposed to be—there, and therefore the existence of some “rights” that would flow from that.
Earlier quoted context omitted.
I think the parent is saying that one should be aware that the whole LLM industry is still in an experimental stage and far from mature. What you want isn’t what’s being offered. I agree that there should be higher standards, but what we currently have is an arms race. The consequence is to factor that into the value proposition and maybe not rely too much on it.
SLAs should be standard for any paid service, especially on the enterprise side, but also on the consumer side. Being immature as a company does not excuse a lack of service delivery.