I don't get the use case for these... Their primary customers are enterprises. Are most enterprises happy with running daily tasks on a third party cloud outside of their ecosystem? I think not. So who are they building these for?
Claude Code Routines
201–210 of 451 posts
Re: Claude Code Routines
#202Earlier quoted context omitted.
AI race to the bottom is a debt game now. Once the party is over somebody will have to pay the bill.
It’s going to be crazy with the explanation they come up with why the us public has to pay to bail out AI for national security. In a way, it’s true if china has superior AI then it’s dominance over US will materialize. But it’s not hard to see how this scenario is being used to essential lie and scam into trillions of debt. Its interesting how the cutthroat space of big tech has manifested into an incidious hyper ca…
Re: Claude Code Routines
#203LLMs 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…
I can’t use Claude Code at all anymore, not even for simple tasks. The output genuinely disgusts me. Like a friend who constantly stabs you in the back.
My favorite AI feature at the moment is the JetBrains predict next edit. It‘s so fast that I don’t lose attention and I’m still fully under control.
Re: Claude Code Routines
#204Earlier quoted context omitted.
I guess there's a pretty clear incentive to nerf the current model right before the next model is about to come out.
Wouldn't that amount to fraud?
Sometimes you have to keep starting new session until it works. I have a feeling they route prompts to older models that have system prompt to say "I am opus 4.6", but really it's something older and more basic. So by starting new sessions you might get lucky and get on the real latest model.
Re: Claude Code Routines
#205Earlier quoted context omitted.
I believe the current game everybody plays is: * make sure the model maxes out all benchmarks * release it * after some time, nerf it * repeat the same with the next model However, the net sum is positive: in general, models from 2026 are better than those from 2024.
yup, after the token-increase from CC from two weeks ago, I'm now consistently filling the 1M context window that never went above 30-40% a few days ago. Did they turn it off? I used to see the Co-Authored by Opus 4.6 (1M Context Window) in git commits, now the advert line is gone. I never turned it on or off, maybe the defaults changed but /model doesn't show two different context sizes for Opus 4.6 I never asked fo…
Re: Claude Code Routines
#206It’s a trap.
Re: Claude Code Routines
#207You'd think that if they were compute-limited ... Trying to get people to use it less ... The rational thing to do would be to not ship features that will use more compute automatedly? Or does this use extra usage?
They are more worried about building a moat than anything else. They want people building integrations that are difficult to undo so that they lock into the platform.
1. Anthropic realized their models weren't enough of a moat.
2. They built tools so they could expand their moat.
3. People don't want to use their tools, they want their models, and use other, better tools.
4. Anthropic bans the use of better tools, taking advantage of their model superiority to try to lock people into subpar tools.
"I don't have enough of a moat so I'll use my little moat and pretend it's a big one" doesn't sound like a great strategy. All they're doing with this anticonsumer behaviour is making sure that I'll leave the moment another model works for me as well as Claude does.
Re: Claude Code Routines
#208Earlier quoted context omitted.
It also beats OC's heartbeat where it auto-runs every 30 minutes and runs a bunch of prompts to see if it actually needed to run or not.
Man, this just bit me too. I started playing with OC over the weekend (in a VM), and the spend was INSANE even though I wasn't doing anything. I don't see this as very useful as an "assistant" that wanders around and anticipates my needs. But I do like the job system, and the ability to make skills, then run them on a schedule or in response to events. But when I looked into what it was doing behind my back, 48 times…
It's very light on token usage in general, as well.
Re: Claude Code Routines
#209I'm a little confused on the ToS here. From what I gathered, running `claude -p ` on cron is fine, but putting it in my Telegram bot is a ToS violation (unless I use per-token billing) because it's a 3rd party harness, right? (`claude -p` being a trivial workaround for the "no 3rd party stuff on the subscription" rule) This Routines feature notably works with the subscription, and it also has API callbacks. So if my…
Anthropic deserves to have this as the top comment on every HN post. It's absurd that they don't clarify this better and so many people are running around online saying the exact opposite from what their, confusing, docs say. The Chilling Effect of this is real and it gets more and more frustrating that they can't or won't clarify.
Re: Claude Code Routines
#210Earlier 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,…
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.
One area that was a little shitty that has changed a lot is egress costs, but we mostly have shifted to engineering around it. I’ve never minded all that much, and AWS support is so good at enterprise tiers that they’ll literally help you do it.