5 ms·
Looks really interesting -- quick question though: how does this differ from hooks (e.g., https://code.claude.com/docs/en/hooks https://code.claude.com/docs/en/
by jb_hn 5mo ago
Looks really interesting -- quick question though: how does this differ from hooks (e.g., https://code.claude.com/docs/en/hooks https://code.claude.com/docs/en/hooks)?
- simonw 5mo agoLooks more similar to routines for me (just launched the other day): https://code.claude.com/docs/en/routines https://code.claude.com/docs/en/routines
- rileyt 5mo agosimonw is right, daemons are closer to routines. compared to routines: - daemons are specified by a DAEMON.md file in the repo (like skills). it's version-controlled and team-owned, not hidden in a dashboard or linked to a single developers account. - daemons have a specialized event pipeline that joins similar webhooks events into a single daemon activation and can inject late arriving events into a daemon that's already running (this is key to avoid duplicate work and noisy actions). - the watch conditions are a more powerful activation method because they use semantic matching and can be mixed with cron schedules. - daemons have access to the logs from their past runs (and soon proper memory) so they can learn from their own mistakes.