Live data from Hacker News

Claude Code Routines

code.claude.com

411–420 of 451 posts

Re: Claude Code Routines

#411
post #245

Earlier quoted context omitted.

They can’t allow third party software because the third parties save the outputs of Claude responses and distill them into new models to compete with Claude.

This distilling sounds wonderful to me as an end user. Is there some place we can donate our chats and output?

There is DataClaw https://github.com/peteromallet/dataclaw which uploads your Claude Code chats and more to HuggingFace in a single command. Nowadays there are many similar tools.

Re: Claude Code Routines

#412

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…

[dead]

Re: Claude Code Routines

#413
post #407

Earlier quoted context omitted.

>You can lessen your dependence on the specific details of how /loop, code routines, etc. work by asking the LLM to do simpler tasks, and instead, having a proper workflow engine be in charge of the workflow aspects. Or, you know, by writing the code yourself?

"You can lessen your dependence on a specific LLM implementation by not using LLMs" is certainly a take but it doesn't really address the root issue of models getting nerfed to save resources after they've gained wide adoption.

A simple task ("convert this file from JS to TS, here are the types of all imported things") is much more likely to continue to work with a nerfed model compared to a complicated task ("convert this repo to TS, make sure to run tsc afterward and fix all errors"). The former is a subtask of the latter!

Taking a moment to create a workflow where these steps are separated (or rather, having an LLM build this workflow) and the LLMs are asked to just do minor leaf tasks increases your resilience to nerfed models.

Re: Claude Code Routines

#414

Earlier quoted context omitted.

Hmm, I can't edit the original comment to retract that edit either. Either my account is flagged for something or HN is being weird.

this comment was made almost 1h after the one at the root of the thread you can make changes to your posts up to 10 minutes after they were originally created — see: https://news.ycombinator.com/newsfaq.html#:~:text=minutes%20...

That is not what that feature does, it just is the time your comment is publically shown.

Users have 2 hours to edit comments, and the button was gone within 1 hour.

Re: Claude Code Routines

#415
post #23

This is one of the best features of OpenClaw - makes sense to swipe it into Claude Code directly. I wonder if Anthropic wants to just make claude a full stand-in replacement for openclaw, or just chip away at what they think the best features are, now that oAI has acquired.

What are some of the best use cases you've found? I have some gh actions set up to call claude code, but those have already been possible.

Well, every time a calendar invite is accepted, it sets up a cron job to check in fifteen minutes before the meeting, and text me the zoom link, for instance. Once setting the cron job itself is free, you could think of a lot of use cases.

Re: Claude Code Routines

#416

Earlier quoted context omitted.

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.

Likewise, I foolishly assumed everybody else was just doing it wrong. But this week I've lost count of the times I've had to say something along the lines of: "Can you check our plan/instructions, I'm pretty sure I said we need to do [this thing] but you've done [that thing]..." And get hit with a "You're absolutely right...", which virtually never happened for me. I think maybe once since Opus 4-6.

maybe a consequence of saving GPU for newer models? Also tuning effort level suppose to help, haven't get enough dp on this though

Re: Claude Code Routines

#417
post #324

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…

The future of harnesses cannot be „resend the whole history on every step“ or whatever this terrible compaction is. Most of the context is unstructured fluff, much of it is distracting or even plain wrong. Especially the „thinking“ tokens are often completely disjoint halucinations that don’t make any sense. I think what will have to happen is that context looks less like a long chat and action log and more like a st…

You’re going to loose a lot of natural language nuances then. Plus git is essentially your structured, validated state description.

Re: Claude Code Routines

#418
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?

The rational thing to do would be to build more data centers. Use that huge influx of money on infrastructure. Make tokens dirt cheap.

Re: Claude Code Routines

#419
post #321

Earlier quoted context omitted.

It's bad at long running tasks.

Yes and no. It's bad because of shorter context but it does have auto-compaction which was much better than Claude. If you provide it documentation to work from and re-reference, it works long-running. Honestly - 'every inch of IQ delta' seems to be worth it over anything else. I'm a long time Claude Code supporter - and I'm ashamed to admit how instantly I dropped it when discovering how much better 5.4 is. I don't…

I tried to use 5.4 for something pretty straightforward - create scripts to automate navigating a game UI and capturing the network traffic. 5.4 was super frustrating, constantly stopping and waiting for feedback etc, even after telling it to never wait and just iterate/debug. I quit and switched to Opus 4.6 and it did much more of the work by itself.

Re: Claude Code Routines

#420
The trigger matrix here is actually the most interesting part. Schedule plus API plus GitHub event on the same routine unlocks some nice patterns, and the /fire endpoint returning a session URL means you can wire this into alerting tools or a CD pipeline from almost anywhere. The part that is not really covered in the docs is what state a routine is supposed to recover from if a previous run died halfway through a repository change. The protection around claude/-prefixed branches helps you not clobber main, but it does not tell the next run what the previous run actually finished. I run scheduled jobs against multi step pipelines on my own infra and the failure mode that bites is not the crash, it is the run that returned success while a downstream side effect quietly broke. The /fire response returns a session URL and a session ID, which tells you the routine started, but how is a routine expected to notice when the downstream thing it kicked off (a CD pipeline, an alert follow-up, a library port PR like the one in the examples quietly fell over five minutes after the session ended?
Post reply on HN