Hacker News Reader

Comment by SyneRyder | Hacker News Reader

I don't think the CLI offers daily routines under the Anthropic subscription anymore?

There's also the cross conversation memory search, which uses a different conversation dataset (the Claude Web / Claude.AI conversations) than Claude Code does. I'm not even sure Claude Code does cross conversation search?

The Desktop interface also presents Markdown as formatted text and presents artifacts (especially interactive ones) better than the CLI can.

All that said - I actually use the CLI for nearly everything (even on Windows). Rather than use Claude Desktop for daily "routines" that are capped at 15 total cron-jobs and use extra usage credits, I think I'll continue building my own minimal harness and move my routines to models from other providers.

View on HN

> There's also the cross conversation memory search, which uses a different conversation dataset (the Claude Web / Claude.AI conversations) than Claude Code does. I'm not even sure Claude Code does cross conversation search?

This is one of the first things I “fixed” with skills and hooks. I index every conversation in SQLite and have a skill which knows what to do when I ask it to search the index. I had to avoid the word memory because it’s too tied up in other parts of the context. It even indexes across my different machines. I set this up because I have terrible context discipline. I’ll go off on a tangent in one context and start planning and sometimes implementing something based on that thread which really deserves its own context. Afterward I can create the new context and move relevant bits to it, but I’d lose that initial starting conversation which inherently has more data than the summary in the new context.

I also use a few different related contexts. One where I’m building a game engine in zig and another talking about game ideas. There’s a lot of back and forth going on there which needs some shared context. I solve this with a combination of Claude.md references and that searchable session index.

Everything I do with scheduled tasks are just wired up with systemd and simple scripts. No LLM in the critical execution path. Again a skill tells CC how I manage those scheduled things so I just have to say something like “run this every day at midnight” and CC has reliably taken care of the rest.

Why not just allow it to grep ~/.claude

Grep is more expensive from a token use standpoint and jsonl files seem to get recycled after 30 days. Grep is what I was using first.

You can increase the life of the JSONL files, if you add this to the settings.json for Claude Code, where you would configure your hooks:

  "cleanupPeriodDays": 99999

That's maybe excessive, but I figure we'll have another solution to this in 273 years. But then, they thought that about the Y2K bug as well.

Love your idea to actually index the conversations though!

> I don't think the CLI offers daily routines under the Anthropic subscription anymore?

It (Claude Code) does, I discovered it by accident recently, having never used daily routines before. Haven't touched Claude Desktop at all, outside of playing with it for 30 mins or so months ago.

TLDR: I used Claude Code to build a command that scrapes job postings from a few employers I am interested in (it is a bit more complicated than that, but that's the gist). At the end CC asked me "do you want me to re-run it daily?" I said yes, and it generated a daily routine and gave me a URL to my anthropic account page where I can see all my daily routines.

There, it says that I am currently using up 1 out of 15 "free" daily routines that come with my personal subscription, and I would have to pay extra if I want to have more than 15 active at a time (I assume by switching to per-token pricing for anything beyond 15, but not sure).

> All that said - I actually use the CLI for nearly everything (even on Windows).

I also haven't touched routines, but I use cc to write automation tasks that will integrate a model when I need an inference layer. Which I also did before routines..

Have people actually been using routines effectively?

That makes sense. Maybe the existing VS Code integration is the place to solve part of this for coding workflows: formatted output, artifacts, and search UI all seem useful next to the editor. The Claude.ai conversation corpus/search seems like the part that may need deeper account integration.

Reply on news.ycombinator.com