hackernews client

Show HN: Cronloop, run Claude Code or Codex on a schedule

1 pointsposted 5 hours ago

3 Comments

miketromba

5 hours ago

Hey HN, I often want to automate recurring tasks with my Claude Code/Codex subscriptions, so I built Cronloop to make this simple.

Just create an agent, set a schedule, connect your existing claude code/codex subscription, give your agent instructions + tools, and boom - you have an autonomous agent running in a loop, working while you sleep.

Every agent has a simple, durable markdown-based memory system. Your agents can self-improve over time - you can include instructions to record learnings with each run for other agents to benefit from.

Some ways I'm using it:

- I built a self-driving events website (aievents.now) and have a cronloop agent for each city that autonomously curates events every morning. - I have a few websites autonomously SEO-optimizing every day based on search console data + keyword research.

Free to try - you can create up to three agents for free to get started.

nakas1

4 hours ago

what makes this better than just /loop in Claude Code?

miketromba

3 hours ago

/loop is sufficient in many simple cases

Cronloop is more of a control plane that makes it nicer & more scalable once you have many agents and need to monitor / refine them over time.

Create & manage unlimited agents in one place, they all run in the cloud - no machine to manage and keep online yourself, easily monitor and analyze runs (agent runs stream in real-time), tune the agent with run duration constraints, give it the ability to self-improve with the built-in durable memory system without having to invent your own, connecting tools is very simple (200+ supported in the connector library).

It also runs codex, not just claude code.

I currently have ~25 cronloop agents running on various models between codex/claude.

Running them all on /loop would be painful and hard to maintain without cronloop or a similar control plane.