Live data from Hacker News

Anthropic downgraded cache TTL on March 6th

github.com

181–190 of 447 posts

Re: Anthropic downgraded cache TTL on March 6th

#181

Changing "regression" to "Anthropic silently downgraded" sensationalizes the story Why the FUD? I notice some interesting public opinion weather change since Anthropic passed OpenAI wrt revenue

From the response in the linked issue: >> Was there a change? Yes — March 6, intentional, part of ongoing cache optimization. You pinpointed the date correctly. The entire issue lays out how and why it's a silent downgrade. Also silent because it just happened, without announcing. I don't understand how is this FUD?

[deleted]

Re: Anthropic downgraded cache TTL on March 6th

#182

Earlier quoted context omitted.

open weights is a way to nerf your opponent and is meaningless to your business if you need to retrain a model because your trailing So, it makes a lot of sense to get people a "demo" and claim the paid product is better. i think a lot of people have no idea how capable local models are atm.

Two years ago a lot of people thought GPT-4o was usable for software development. I didn’t really find that to be the case in general but certainly it could do a lot of useful things. And now Qwen3.5-8B is just as capable and runs fine on an M2 MacBook Air.

QWEN3.5 coder next runs to ~84k context before it poops out on AMD395+ w/128GB. Most of what it's good at is boilerplate find/replace/copy/paste; but being able to scaffold things out and touch up 20-30% of the code is pretty sweet.

Re: Anthropic downgraded cache TTL on March 6th

#183

Has anybody else noticed a pretty significant shift in sentiment when discussing Claude/Codex with other engineers since even just a few months ago? Specifically because of the secret/hidden nature of these changes. I keep getting the sense that people feel like they have no idea if they are getting the product that they originally paid for, or something much weaker, and this sentiment seems to be constantly spreadin…

The past two weeks I've had code that was delivered and declared as done (it did pass tests) but failed in a review by Codex. This has looped to a painful extent. The code in question deals with concurrency issues so there's an acknowledgement that its tricker, but still, I expect more from Claude.

Re: Anthropic downgraded cache TTL on March 6th

#184
Lately I am finding myself doing more and more of what I called "ambient coding" so that I am not directly using anymore all of those coding harnesses.

https://redbeardlab.gitbook.io/acem/essays/ambient-developme...

I basically wrote a small GitHub app and I simply create a GitHub issue, the bot read it, run an LLM loop and come up with a PR (or a design)

Then I simply approve the pr (or the design)

I find it much calmer and much more productive

Re: Anthropic downgraded cache TTL on March 6th

#185
post #170

Earlier quoted context omitted.

In this case, they handled things pretty well. You can still use openclaw etc with your regular Anthropic subscription, it will just count towards your extra credits / usage which you can buy for a 30% discount compared to API pricing. And they gave everyone one month’s value in credits. I don’t think they could have done that much better I’d say.

That does not address joshstrange's concerns. There is very poor clarity about what is and isn't allowed with the Claude SDK/claude -p. Are we allowed to use it to automate stuff? What kind of tasks is it permitted to be used for? What if you call your script 'OrangeClaw' and release that on GitHub? What if your script gets super popular, does it suddenly become against TOS?

This is exactly my point. At what point does it become a ToS violation? Right now it's a huge grey area and the idea of getting my account banned because I crossed an invisible line with zero recourse other than to switch providers is... frustrating.

Re: Anthropic downgraded cache TTL on March 6th

#186
post #65

Has anybody else noticed a pretty significant shift in sentiment when discussing Claude/Codex with other engineers since even just a few months ago? Specifically because of the secret/hidden nature of these changes. I keep getting the sense that people feel like they have no idea if they are getting the product that they originally paid for, or something much weaker, and this sentiment seems to be constantly spreadin…

Well, off the top of my head: - Banning OpenClaw users (within their rights, of course, but bad optics) - Banning 3rd party harnesses in general (ditto) (claude -p still works on the sub but I get the feeling like if I actually use it, I'll get my Anthropic acct. nuked. Would be great to get some clarity on this. If I invoke it from my Telegram bot, is that an unauthorized 3rd party harness?) - Lowering reasoning eff…

> (claude -p still works on the sub but I get the feeling like if I actually use it, I'll get my Anthropic acct. nuked. Would be great to get some clarity on this. If I invoke it from my Telegram bot, is that an unauthorized 3rd party harness?)

How often? Realistically, if you invoke it occasionally, for what's clearly an amount that's "reasonable personal use", then no you don't get nuked.

Re: Anthropic downgraded cache TTL on March 6th

#187
post #170

Earlier quoted context omitted.

That does not address joshstrange's concerns. There is very poor clarity about what is and isn't allowed with the Claude SDK/claude -p. Are we allowed to use it to automate stuff? What kind of tasks is it permitted to be used for? What if you call your script 'OrangeClaw' and release that on GitHub? What if your script gets super popular, does it suddenly become against TOS?

This is exactly my point. At what point does it become a ToS violation? Right now it's a huge grey area and the idea of getting my account banned because I crossed an invisible line with zero recourse other than to switch providers is... frustrating.

It's pretty easy to read between the lines tbh. Personal, non-automated use is fine. Using it as a means to automate depleting your 5-hour limit 24/7 ("leftover usage") is not fine. They don't want to put in in the ToS because it's almost impossible because writing what I just said will still have people going "well what's automated, where's the exact line!" when it's all pretty clear what the intended use case here is. The Anthropic peeps have said about as much.

I get that the traditional dev is allergic to the concept of reading between the lines and demands everything to be spelled out explicitly, but maybe you should just see it as something to learn because it's an incredibly useful life skill.

Re: Anthropic downgraded cache TTL on March 6th

#188
post #74

Earlier quoted context omitted.

A month ago the company I work at with over 400 engineers decided to cancel all IDE subscriptions (Visual Studio, JetBrains, Windsurf, etc.) and move everyone over to Claude Code as a "cost-saving measure" (along with firing a bunch of test engineers). There was no migration plan - the EVP of Technology just gave a demo showing 2 greenfield projects he'd built with Claude Opus over a weekend and told everyone to copy…

Pretty bad decision on his part. I've been telling other engineers within my company who felt threatened by AI that this would happen. That prices would rise and the marginal cost for changes to big codebases would start to exceed the cost of an engineer's salary. API credits are expensive, especially for huge contexts, and sometimes the model will use $200 in credits trying to solve a problem that could be fixed in…

> the model will use $200 in credits trying to solve a problem that could be fixed in an hour by a good engineer with enough context

So the price for fixing the problem is equal. Sounds like a great argument for AI.

Re: Anthropic downgraded cache TTL on March 6th

#189
post #187

Earlier quoted context omitted.

This is exactly my point. At what point does it become a ToS violation? Right now it's a huge grey area and the idea of getting my account banned because I crossed an invisible line with zero recourse other than to switch providers is... frustrating.

It's pretty easy to read between the lines tbh. Personal, non-automated use is fine. Using it as a means to automate depleting your 5-hour limit 24/7 ("leftover usage") is not fine. They don't want to put in in the ToS because it's almost impossible because writing what I just said will still have people going "well what's automated, where's the exact line!" when it's all pretty clear what the intended use case here…

Ok, let's say I'm not using it to deplete leftover usage, the task just happens to run down the 5 hour window usage.

Are you willing to bet your account over whether you've read between the lines correctly? Anthropic aren't going to listen to appeals.

Re: Anthropic downgraded cache TTL on March 6th

#190
post #189
post #187

Earlier quoted context omitted.

It's pretty easy to read between the lines tbh. Personal, non-automated use is fine. Using it as a means to automate depleting your 5-hour limit 24/7 ("leftover usage") is not fine. They don't want to put in in the ToS because it's almost impossible because writing what I just said will still have people going "well what's automated, where's the exact line!" when it's all pretty clear what the intended use case here…

Ok, let's say I'm not using it to deplete leftover usage, the task just happens to run down the 5 hour window usage. Are you willing to bet your account over whether you've read between the lines correctly? Anthropic aren't going to listen to appeals.

> the task just happens to run down the 5 hour window usage.

In a single prompt? From zero usage? That doesn't "just happen".

Post reply on HN