Show HN: Daemons – we pivoted from building agents to cleaning up after them (charlielabs.ai)

70 points by rileyt ↗ HN
For almost two years, we've been developing Charlie, a coding agent that is autonomous, cloud-based, and focused primarily on TypeScript development. During that time, the explosion in growth and development of LLMs and agents has surpassed even our initially very bullish prognosis. When we started Charlie, we were one of the only teams we knew fully relying on agents to build all of our code. We all know how that has gone — the world has caught up, but working with agents hasn't been all kittens and rainbows, especially for fast moving teams.

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 ] thread
[flagged]
The pivot framing is refreshingly honest. Most agent startups double down when the next model release makes half their scaffolding obsolete. Drift detection is the right insight though — you end up with more cleanup work than creation work once the agent output volume outpaces your review capacity. Curious how you handle the case where the "drift" is actually a real intent change the human hasn't formalized yet.
Looks pretty interesting, will try it out and give you feedback! keep up the good work.
The schedule is cute.

"Complete non-determinism for everything except the schedule it runs at."

How would this work? One would connect it's repository to a cloud platform that would then act based on the existing daemons of the repo?
I feel like I must have missed something important, but I don't feel like I skipped anything.

It seems like everything is telling me to talk to Charlie to get setup. _How_ do I talk with Charlie?

(comment deleted)
I can not find a description of how it works on the site, magic hands daemons !

Cool story, but what runs when?

tl;dr : https://charlielabs.ai/how-it-works/ and https://docs.charlielabs.ai/daemons

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.

I might try your tool but from my experience PR review and the general state of AI improvement for code is just fu*ing awful. Oh I forgot to ident three lines of code thanks buddy how about this massive memory leak instead that’s of actual value to anyone?
Looks incredible neat! I'll give it a try! Congrats!