Show HN: Daemons – we pivoted from building agents to cleaning up after them (charlielabs.ai)
The one thing we've noticed over the last 3 months is that the more you use agents, the more work they create. Dozens of pull requests means older code gets out of date quickly. Documentation drifts. Dependencies become stale. Developers are so focused on pushing out new code that this crucial work falls through the cracks. That's why we pivoted away from agents and invented what we think is the necessary next step for AI powered software development.
Today, we're introducing Daemons: a new product category built for teams dealing with operational drag from agent-created output. Named after the familiar background processes from Linux, Daemons are added to your codebase by adding an .md file to your repo, and run in a set-it-and-forget-it way that will make your lives easier and accelerate any project. For teams that use Claude, Codex, Cursor, Cline, or any other agent, we think you'll really enjoy what Daemons bring to the table.
22 comments
[ 2.9 ms ] story [ 54.0 ms ] threadAre the two competitive or additive?
- example daemon files: https://github.com/charlie-labs/daemons
- reference docs: https://docs.charlielabs.ai/daemons
happy to answer questions. all feedback appreciated.
"Complete non-determinism for everything except the schedule it runs at."
It seems like everything is telling me to talk to Charlie to get setup. _How_ do I talk with Charlie?
Cool story, but what runs when?
to get started, look at https://docs.charlielabs.ai/installation, but essentially
1) signup with your github login
2) install the CharlieCreates GitHub App on the repos you want Charlie to work in
3) create an issue, tag @CharlieHelps to help you create your first daemon!
the daemon will run on the charlie runtime and follow the watch / schedule conditions you set in your DAEMON.md file
full disclosure: i am part of the engineering team behind this.