What are routines

A routine is something I set up once and it runs on its own. No daily effort from me. Think of it this way: you decide something should happen every Monday at 8 AM, or that whenever X happens, Y should trigger automatically. This frees up mental space for things you can't automate.

In Claude Code I ask Claude to set something up. He creates everything needed—watches the clock, checks conditions, runs it at the right moment. I just check in now and then to make sure it's doing what I intended.

I had routines before, when I was doing different work. Now I focus mainly on the web and content, so I have fewer automated things. Not because I miss them, but because not everything is worth automating. Sometimes it's simpler to just do the thing yourself.

How they work

Claude builds instructions that run based on time or some condition. Everything runs on my machine in the background, without forcing me to do anything. If something goes wrong, Claude logs it and I can read the details. When I need a change, I ask him to adjust it.

It's not magic. It's just ordering steps so they run without my presence. But here's the real part: the more you automate, the more you have to monitor whether it's working right. Sometimes setting up a routine costs more time than just doing the task. The key is knowing when automation makes sense and when it doesn't.

What I have set up

Honestly? I don't have much scheduled right now. I'm focused on the web and content, and what doesn't need to run automatically, I do myself.

I had routines before. They ran regularly, tracked data, calculated results, made decisions on their own about what came next. All of that is archived now. I decided to focus on something different. Those things sit idle if at all, but they're not part of my daily workflow anymore.

Now when I need something repeated, I ask Claude to set it up. But I don't chase automation for its own sake. The more runs automatically, the more you have to watch whether it's actually working. Sometimes it's easier to do the thing yourself than spend half a day setting it up and then troubleshooting what broke. The point is understanding when something is worth automating and when it isn't.