Live data from Hacker News

Claude Code Routines

code.claude.com

221–230 of 451 posts

Re: Claude Code Routines

#221

LLMs and LLM providers are massive black boxes. I get a lot of value from them and so I can put up with that to a certain extent, but these new "products"/features that Anthropic are shipping are very unappealing to me. Not because I can't see a use-case for them, but because I have 0 trust in them: - No trust that they won't nerf the tool/model behind the feature - No trust they won't sunset the feature (the graveya…

This echoes my thoughts exactly. I've tried to stay model-agnostic but the nudges and shoves from Anthropic continue to make that a challenge. No way I'm going that deep into their "cloud" services, unless it's a portable standard. I did MCP and skills because those were transferrable. I also clearly see the lock-in/moat strategy playing out here, and I don't like it. It's classic SV tactics. I've been burned too man…

Agree. I just don't think it's realistic to expect the technology to not become a tool for commercialism. It plays out the same way every time: technology arrives, mass adoption with idealist intentions, somebody has to pay the mortgage, delight disappears.

Woz has been saying this for decades, we went from buying a computer and owning it to being trapped inside someone else's platform. MCP being open was a good sign but I'm watching how tightly Routines gets coupled to their stack.

Re: Claude Code Routines

#222
Seems like more vendor lock-in tactics.

Not saying it doesn’t look useful, but it’s something that keeps you from ever switching off Claude.

Next year, if Claude raises rates after getting bought by Google… what then?

And what happens when Claude goes down and misses events that were supposed to trigger Routines? I’m not at the point where I trust them to have business-dependable uptime.

Re: Claude Code Routines

#223

Earlier quoted context omitted.

This is a similar sentiment I heard early on in the cloud adoption fever, many companies hedged by being “multi cloud” which ended up mostly being abandoned due to hostile patterns by cloud providers, and a lot of cost. Ultimately it didn’t really end up mattering and the most dire predictions of vendor lock in abuse didn’t really happen as feared (I know people will disagree with this, but specifically speaking abou…

> specifically speaking about aws, the predictions vs what actually happened is a massive gap I guess I'm one of the people who disagree, specifically about AWS. I think a lot of companies just watch their bill go up because they don't have the appetite to unwind their previous decision to go all-in on AWS. Ignoring egress fees, migrating storage and compute isn't hard, it's all the auxiliary stuff that's locked in,…

I am curious, what do people use Cognito for? I’ve never not ended up regretting using it.

Re: Claude Code Routines

#224
post #154

Earlier quoted context omitted.

Serious question, do we actually know what we're paying for? All I know is it's access to models via cli, aka Claude Code. We don't know what models they use, how system prompt changes or what are the actual rate limits (Yet Anthropic will become 1 trillion dollars company in a moment).

> We don't know what models they use, how system prompt changes or what are the actual rate limits (Yet Anthropic will become 1 trillion dollars company in a moment). Not just that, but there’s really no way to come to an objective consensus of how well the model is performing in the first place. See: literally every thread discussing a Claude outage or change of some kind. “Opus is absolutely incredible, it’s one sh…

> See: literally every thread discussing a Claude outage or change of some kind. “Opus is absolutely incredible, it’s one shotting work that would take me months” immediately followed by “no it’s totally nerfed now, it can’t even implement bubble sort for me.”

Funny: I’m literally, at this very moment, working on a way to monitor that across users. Wasn’t the initial goal, but it should do that nicely as well ^^

Re: Claude Code Routines

#226

Earlier quoted context omitted.

> specifically speaking about aws, the predictions vs what actually happened is a massive gap I guess I'm one of the people who disagree, specifically about AWS. I think a lot of companies just watch their bill go up because they don't have the appetite to unwind their previous decision to go all-in on AWS. Ignoring egress fees, migrating storage and compute isn't hard, it's all the auxiliary stuff that's locked in,…

the AWS things you mentioned you don’t need to mess with at all, with the exception of IAM, which doesn’t cost anything at all. your experience just hasn’t been my experience I guess. The more managed the service you use, the more costs you are going to pay - for a very long time I’ve got by with paying for compute, network, and storage on the barebones services. If you want to pay for convenience you will pay for it…

> the AWS things you mentioned you don’t need to mess with at all

not the op, but I suspect they were meaning it's a huge pain migrating to a different cloud provider when all those features mentioned are in use. not that managing them is a mess in AWS.

Re: Claude Code Routines

#227
post #107

Unrelated, but Claude was performing so tragically last few days, maybe week(s), but days mostly, that I had to reluctantly switch. Reluctantly because I enjoy it. Even the most basic stuff, like most python scripts it has to rerun because of some syntax error. The new reality of coding took away one of the best things for me - that the computer always just does what it is told to do. If the results are wrong it mean…

Codex with 5.4 xhigh. It's a bad communicator but does the job.

You mean codex (client) with GPT 5.4 xhigh? I am using Codex 5.3 (model) through Cursor, waiting for Codex 5.4 model as I had great experience so far with 5.3.

Re: Claude Code Routines

#228
post #48
post #41

Earlier quoted context omitted.

They’re shooting themselves in the foot with these dumb restrictions.

They are not dumb restrictions. They just don't have the compute. That is the dumb part. Dario did not secure the compute they need so now they are obviously struggling.

It’s dumb to piss off their customers with confusing rule changes instead of just raising their prices to deal with high demand. They might even make a profit

Re: Claude Code Routines

#229

LLMs and LLM providers are massive black boxes. I get a lot of value from them and so I can put up with that to a certain extent, but these new "products"/features that Anthropic are shipping are very unappealing to me. Not because I can't see a use-case for them, but because I have 0 trust in them: - No trust that they won't nerf the tool/model behind the feature - No trust they won't sunset the feature (the graveya…

Many of the new features in claude code have soon been implemented in other harnesses, for example plugins/skills. After all it is just a prompt.

Re: Claude Code Routines

#230
post #49

Anthropic is really good at releasing features that are almost the same but not exactly the same as other features they released the week before

That's a fairly decent defintion of vibecoding across multiple sessions.
Post reply on HN