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

381–390 of 451 posts

Re: Claude Code Routines

#381

Post by stingraycharles »

pkulak wrote: post #43
andai wrote: post #20

Earlier 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…

I can recommend Hermes Agent as an alternative to OpenClaw which actually works well, is properly architected, and doesn’t break three times a week.

Re: Claude Code Routines

#385

Post by mrgill »

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…

Don't use claude -p in any kind of harness at all. I used it ONCE in a local custom made one, and got my account nuked. No help from them at all. Appealed, and the appeal was denied. I had been a Max subscriber since day 1 and Claude subscriber since day 1 in 2023. They don't care.

Re: Claude Code Routines

#386

Post by rbalicki »

spprashant wrote: post #193
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…

I think it behooves us to be selective right now. Frontier labs maybe great at developing models, but we shouldn't assume they know what they are doing from a product perspective. The current phase is throwing several ideas on the wall and see what sticks (see Sora). They don't know how these things will play out long term. There is no reason to believe Co-work/Routines/Skills will survive 5 years from now. So it mig…

You may want to check out Barnum, which is a programming language/agent orchestration tool that makes it easy to build things like /loop, or Claude code routines. And you won't end up dependent on the specifics of how Claude code routines work!

https://github.com/barnum-circus/barnum

Re: Claude Code Routines

#387

Post by simmonmt »

munksbeer wrote: post #371
Nevermark wrote: post #266

Earlier quoted context omitted.

> Claude Code’s "Memory" feature was the tipping point for me My standing orders are the default MEMORY.md must be a stub directing Claude to another MEMORY.md file in the local folder, project, etc. All memories remain with their respective projects over syncs, moves, devices, etc. The stub must state all this clearly, and nothing else. This has worked very well. If you give the model/memory a name, that name can be…

Can you explain a bit more technically how you set this up? What is a "stub directory"? Feel free to give a concrete example if you have time, because this sounds like something I definitely want to try out myself.

I think he meant a very small (stub) MEMORY.md whose sole contents are something like "don't write here - write there".

Re: Claude Code Routines

#388

Post by comboy »

taspeotis wrote: post #212
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…

https://marginlab.ai/trackers/claude-code/

I think API is fine, likely only subscription is affected. Not to mention trivial heuristics to differentiate repeated API calls / same data and potential CLI usage although that would be true malice.

It seemed to me that it was performing better through opencode using API but did not test extensively.

Re: Claude Code Routines

#389

Post by rowanG077 »

dzink wrote: post #245
ElFitz wrote: post #220

Earlier quoted context omitted.

> Not because I can't see a use-case for them, but because I have 0 trust in them > […] > Put another way, LLM companies are trying to climb the ladder to be a platform, I have zero interest in that, I was a "dumb pipe", I want a commodity, I want a provider, not a platform. That is my sentiment precisely, and a big reason why I’ve started moving away from Claude Code in the past few weeks when I realised how much of…

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.

Of course they can allow it. They choose not to. They choose to screw over all users because they are afraid of some company making a claude ripoff. It shows a lack of faith in their own engineering. It shows a lack of respect for users.

Re: Claude Code Routines

#390

Post by baq »

michaeldwan wrote: post #217
fragmede wrote: post #185

Earlier quoted context omitted.

There's a tiny amount of friction. Enough that I'll be honest and say that I spend the majority of my time with one vendor's system, but compared the to the fiction of moving from one cloud to another, eg AWS to GCP, the friction between opening Claude code vs codex is basically zero. Have an active subscription and have Claude.md say "read Agents.md". Claude Code routines sounds useful, but at the same time, under A…

you're spot on. I use both Claude Code + OpenCode with many different models and friction is minimal as long as I'm deliberate about it. Hell, even symlinking AGENTS.md to CLAUDE.md is like 80% there. It's just portability v convenience. But unlike ~15 years ago with cloud compute, it _feels_ like more people are skeptical of convenience, which is interesting.

> skeptical of convenience

it's not that; it's awareness of inevitability of enshittification. they've released convenient tools, realized there's value to milk and are firing on all cylinders to capture 120% of it. great for IPO, not so great for customers in the long run.

Post reply on HN