Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code Routines

code.claude.com

Post reply on HN
Print view View original

111–120 of 451 posts

Re: Claude Code Routines

#111

Post by dvfjsdhgfv »

palata wrote: post #93
joshstrange wrote: post #66

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…

> - No trust that they won't nerf the tool/model behind the feature I actually trust that they will.

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.

Re: Claude Code Routines

#112

Post by sunnybeetroot »

joshstrange wrote: post #66

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…

Isn’t that what LangChain/LangGraph is meant to solve? Write workflows/graphs and host them anywhere?

Re: Claude Code Routines

#113

Post by giancarlostoro »

dacox wrote: post #90
giancarlostoro wrote: post #86

Earlier quoted context omitted.

I've been talking to friends about this extensively, and read all sorts of different social media posts on X where people deep dove things (I'm at work so I don't have any links handy - though I did submit one on HN, grain of salt, unsure how valid it is but it was interesting: https://news.ycombinator.com/item?id=47752049 ). I think the real issue stems from the 1 Million token context window change. They did not an…

Yeah, I have been seeing lots of comments, tweets, etc, but given everything I have learned about these models - i do not think the change to 1M was innocuous. I'm not sure what they've claimed publicly, but I'm fairly certain they must be doing additional quantization, or at minimum additional quantization of the KV cache. Plus, sequence length can change things even when not fully utilized. I had to manually re-ena…

I used the heck out of it when it was announced, and it felt like I was using one of the best models I've ever used, but then so were all of their other customers, I don't think they accounted for such heavy load, or maybe follow up changes goofed something up, not sure. Like I said, the 1M token, for the first few days allowed me to bust out some interesting projects in one session from nothing to "oh my" in no time.

I'm thinking they should go back to all their old settings and as a user cap you at their old token limit, and ask you if you want to compact at your "soft" limit or burst for a little longer, to finish a task.

Re: Claude Code Routines

#114

Post by deadfall23 »

summarity wrote: post #5

If you’re trying this for automating things on GitHub, also take a look at Agentic Workflows: https://github.github.com/gh-aw/ They support much of the same triggers and come with many additional security controls out of the box

Why not https://github.com/anthropics/claude-code-action?

Re: Claude Code Routines

#115

Post by sidrag22 »

throwup238 wrote: post #77
joshstrange wrote: post #62

Earlier quoted context omitted.

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.

It’s also absurd that they’re doing their communication on a bunch of separate platforms like HN, Reddit, and Github with no coherent strategy or consistency as far as I can tell. Can’t I just get policy clarifications in my email like a normal business? I downgraded my $200/mo sub to $20 this past week and I’m going to try out Codex’s Pro plans. Between the cache TTL (does it even affect me? No idea), changes in the…

I was "Claude only" for well over a year. Kinda crazy how they seem to be gaining a LOT of public attention the last few months, yet i see this type of sentiment from other devs/myself. for me it started with their opencode drama, and openai's decision to embrace opencode in response.

I didn't even know what opencode was prior to that drama, yet now here i am using opencode and a ton of crafted openai agents in my projects. Would love to have some claude agents in that mix, but i guess im stuck in Claude Code if i wanna even touch their models... I'd love to go back to just claude as i "trust" them more in a sorta less evil vibe manner, but if they are gonna prevent subscription usage to something people use to allow themselves more freedom, they gotta then close that gap with their own tools rather than pumping out stuff like this which scares me off given the past couple months.

I totally understand why they are cutting off 3pa access to stuff like openclaw, where the avg user is just a power user in comparison to avg claude user or whatever. I haven't kept up a ton with their opencode issues, but I just know i can't get behind a company actively trying to make my potential usage of tokens less optimized to keep me locked into their ecosystem.

Really just kinda hoping local models kill it all for devs after a few years, I'm not interested in perma relying on data centers for my workflow.

Re: Claude Code Routines

#116

Post by pacha3000 »

comboy wrote: 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…

I'm the first to be tired of everyone, for every model, that says "uuuh became dumber" because I didn't believe them

... until this week! Opus is struggling worse than Sonnet those last two weeks.

Re: Claude Code Routines

#117

Post by oxag3n »

Are they going to mirror every tool software engineers were used to for decades, but in a mangled/proprietary form?

I think to become really efficient they'll have to invent new programming language to eliminate all the ambiguity and non-determinism. Call it "prompt language", with ai-subroutines, ai-labels and ai-goto.

Re: Claude Code Routines

#118

Post by snek_case »

dvfjsdhgfv wrote: post #111
palata wrote: post #93

Earlier quoted context omitted.

> - No trust that they won't nerf the tool/model behind the feature I actually trust that they will.

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.

I guess there's a pretty clear incentive to nerf the current model right before the next model is about to come out.

Re: Claude Code Routines

#119

Post by causal »

andai wrote: post #25

I'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…

Yeah in the span of a month or so we had:

- SDK that allows you to use OAuth authentication!

- Docs updated to say DO NOT USE OAUTH authentication unless authorized! [0]

- Anthropic employee Tweeting "That's not what we meant! It's fine for personal use!" [1]

- An email sent out to everyone saying it's NOT fine do NOT use it [2]

Sigh.

[0] https://code.claude.com/docs/en/agent-sdk/overview#get-start...

[1] https://www.reddit.com/r/ClaudeAI/comments/1r8et0d/update_fr...

[2] https://news.ycombinator.com/item?id=47633396

Re: Claude Code Routines

#120

Post by dpark »

ctoth wrote: post #6

You'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.
Post reply on HN