3 ms·

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

1 points by miketromba 2mo ago

miketromba 2mo 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 2mo ago
what makes this better than just /loop in Claude Code?
- miketromba 2mo 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.
adkornev 2mo ago
What do you do when an agent needs a human decision mid-run? Does Cronloop notify you somehow?
- miketromba 2mo ago
  Real human-in-the-loop is not supported, cronloop is designed for use cases that benefit from full agent autonomy. You can, however, continually monitor and steer the agent by refining its instruction set / memory to improve it over time so that it makes better decisions itself. I have claude connected to the Cronloop MCP and occasionally ask it to analyze the previous N runs of my agent to see if its instructions should be adjusted.

1 points by miketromba 2mo 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 2mo ago

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

miketromba 2mo 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.

adkornev 2mo ago

What do you do when an agent needs a human decision mid-run? Does Cronloop notify you somehow?

miketromba 2mo ago
Real human-in-the-loop is not supported, cronloop is designed for use cases that benefit from full agent autonomy. You can, however, continually monitor and steer the agent by refining its instruction set / memory to improve it over time so that it makes better decisions itself. I have claude connected to the Cronloop MCP and occasionally ask it to analyze the previous N runs of my agent to see if its instructions should be adjusted.