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

441–450 of 451 posts

Re: Claude Code Routines

#441

Post by dgellow »

taytus wrote: post #92
dgellow wrote: post #50

Earlier quoted context omitted.

Their growth over the past months has been more than insane. It’s completely expected they don’t have the compute. You don’t have infinite data centers around

Like or not, openai isn't having the same compute strain, meaning this was predictable.

Or that they were more likely to take risks. It’s not clear to me that what anthropic did is a mistake, they didn’t have the same level of capital and OpenAI is taking extreme risks with their compute commitment. It’s really not obvious that won’t backfire

Re: Claude Code Routines

#442

Post by fredericgalline »

airstrike wrote: post #16

Still no moat. The reason someone would use this vs. third-party alternatives is still the fact that the $200/mo subscription is markedly cheaper than per-token API billing. Not sure how this works out in the long term when switching costs are virtually zero.

[dead]

Re: Claude Code Routines

#443

Post by schlesimeister »

Nevermark wrote: post #429
simmonmt wrote: post #387

Earlier quoted context omitted.

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

Here it is. The independent journalling and notes is a trip. Independent framing and perspective keeping is a really great thing to get from models. It helps them create their own creative constraints. They reason better and are more likely to invent novel solutions. And their self-directed notes can be surprisingly helpful, and ... surprising! It can be amazing and encouraging, to see them pick up on project themes…

This is pretty close to what I've been working on. I'm building a CLI tool called fai that formalises a lot of what you're doing here — context lives in Markdown files in the project (we call it a vault), syncs with git, travels with the project across devices and tools. The session start/end review you're doing manually is baked into the workflow – fai captures decisions, patterns, and notes during a session and digests them at the end so the next session starts with a meaningful summary rather than a blank slate.

The independent journalling angle is interesting. We have a similar concept where the AI maintains its own notes separate from the shared project context. What you're calling Claudius's independent perspective, we'd call the session layer. Still in early release but the core mechanic is the same thing you've landed on... context that belongs to the project, not the platform.

Re: Claude Code Routines

#444

Post by yencabulator »

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…

Also, remember the code quality in the accidental Claude Code source publishing? Expect that for all their features. Thinking about having to debug automations hidden by their SaaS gives me the shudders.

Re: Claude Code Routines

#446

Post by bluegatty »

winrid wrote: post #438
bluegatty wrote: post #432

Earlier quoted context omitted.

I've never run into that problem, but these were coding solutions in codex with a strong plan, steps to work towards. It could be that if you're using massive tokens on a 'plan' then then want to limit u in a way, or even if the objective is not perfectly clear they don't want semi-random token use. See if the token/sub solution behaves differently. Make sure that when it 'compacts' that it re-reads your instructions…

nope

Well I wish I could help - but things changes so fast - codex with opus 4.7 is not very strong. you have to set the effort level relatively high though.

Re: Claude Code Routines

#448

Post by _blk »

varispeed wrote: post #205
_blk wrote: post #133

Earlier quoted context omitted.

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…

I find this 1M context bollocks. It's basically crap past 100k.

I like not running into the mandatory compaction but I do try to actively keep it under too. From an Anthropic standpoint with the new(ish) 5min cache timeout, it's a great way to get people to burn tokens on reinitializing the cache without having them occupy TPU time.. Esp. the larger the context gets.
Post reply on HN