miketromba

There’s a horizontal body overflow bug on this page on mobile. The irony

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.

/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.

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.

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

Just click "New agent", set a schedule, connect your existing claude code/codex subscription, give your agent instructions, connect the tools it needs, and boom - you have an autonomous agent running in a loop, working while you sleep.

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.

Some features:

- Every agent runs in an ephemeral, isolated sandbox - You can monitor runs in real-time (the agent logs stream into the app) - 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. - You can leverage your existing claude code/codex subscriptions or bring your own API key. - 200+ connectors are ready-to-go - connect your agents to any tool that has an MCP, CLI, SDK, API, etc. - You can configure the agent's environment with a setup shell script if needed for greater flexibility

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

You bring your own inference, so cronloop is very generous with usage, the pro plan offers unlimited agents with up to a 5 min interval on runs for $25/mo (or $20/mo annual).

I'm a huge Cronloop user and get a lot of value from it, so I'm excited to share it. Let me know your thoughts!

*Hand-written comment, no AI

This is very good - I have found that well-designed progressive disclosure systems like this tend to be far more effective and performant than cookie-cutter semantic / encoding-based RAG systems. Agents seem to love tables of contents.

I get this. Just shipped the ability to create and edit themes locally, no auth required. The local theme gets persisted to localstorage and you can optionally save/share it later. It also works seamlessly with the fork / import features, so those can be used without auth as well.

Just shipped a fix, middle-click should work now. Thanks for the feedback

Global border radius is editable, that setting is at the bottom of the sidebar. The challenge with global shadcn theming is that you're limited to adjusting the css variables they provide. I believe there is a global spacing variable, but it is not so specific that you can target e.g. just label spacing. That would be something you could modify directly within your shadcn input components via adjusting the tailwind class(es).

Tweakcn is a great tool too. Main difference is I'm hoping ShadcnThemer will be more of a community-driven hub for sharing, starring, and forking themes - similar to how color palette websites have 1000's of user-made palettes. (I took this approach when building the Theme Studio for VS Code and it worked really well, 1000's of themes were designed and shared.)

Tweakcn also charges $ users to be able to share and save themes which I think is silly for a tool like this, should be 100% free and open source.

I also prefer the simple UX of ShadcnThemer better but I'm biased of course.