Show HN: Daemons – we pivoted from building agents to cleaning up after them
Article
TL;DR
Persistent background processes that monitor, coordinate, and clean up after AI agents in your repo.
Key Takeaways
- Daemons are stateful long-running observers; hooks are stateless event-triggered — different mental model.
- Solves multi-agent file conflicts via lease-based locks and per-agent git worktrees.
- Website lacks clear explanation of runtime mechanics — community had to ask how it works.
Discussion
Top comments:
- [jb_hn]: How does this differ from Claude Code hooks already in the platform?
- [newsdeskx]: Hooks are event-driven; daemons are stateful observers — cron vs. running service analogy
- [mkalkere]: Lease-based file locks with git worktrees per agent eliminates multi-agent merge conflicts
- [potter098]: Drift detection needs ordering constraints — do daemons declare dependencies or run isolated?