- Looks really interesting -- quick question though: how does this differ from hooks (e.g., https://code.claude.com/docs/en/hooks)?
by potter098
2 subcomments
- The drift detection angle is interesting. I'd be curious how you handle cases where two daemons touch related files — is there a way to declare ordering constraints in the .md file, or do they run in isolated branches?
- here are a few more resources:
- example daemon files: https://github.com/charlie-labs/daemons
- reference docs: https://docs.charlielabs.ai/daemons
happy to answer questions. all feedback appreciated.
by razvanneculai
0 subcomment
- Looks pretty interesting, will try it out and give you feedback! keep up the good work.
- 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?
by handfuloflight
1 subcomments
- How does this compare to OpenProse, it looks similar? https://openprose.ai/
Are the two competitive or additive?
- 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?
- the hook model is event-driven - something happens, hook fires. daemons sound like they're proposing a different mental model where you have persistent processes that observe and react. the difference is the same as cron vs a running service. both work but the daemon approach makes sense when you need stateful observation across multiple events rather than just per-action triggers
- The schedule is cute.
"Complete non-determinism for everything except the schedule it runs at."
- I can not find a description of how it works on the site, magic hands daemons !
Cool story, but what runs when?
by panosfilianos
2 subcomments
- Why couldn't these just be callable skills?
by j_gonzalez
0 subcomment
- [dead]
by nexustoken
0 subcomment
- [dead]
by builderminkyu
0 subcomment
- [dead]
Hacker News