Hacker Newsnew | past | comments | ask | show | jobs | submit | jb_hn's commentslogin

Very cool! Seems like this would be a great way to support group planning (e.g., "work with friend-1-agent, ..., friend-n-agent to [plan a trip, organize a dinner, etc.]")

Looks really interesting -- quick question though: how does this differ from hooks (e.g., https://code.claude.com/docs/en/hooks)?

Looks more similar to routines for me (just launched the other day): https://code.claude.com/docs/en/routines

simonw 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.


I didn't notice any signs of AI writing until seeing this comment and re-reading (though I did notice it on the second pass).

That said, I think this article demonstrates that focusing on whether or not an article used AI might be focusing on the wrong “problem.” I appreciate being sensitive to the "smell" (the number of low-effort, AI posts flying around these days has made me sensitive too), but personally, I found this article both (1) easy to read and (2) insightful. I think the number of AI-written content lacking (2) is the problem.


Your initial focus is to prioritize which content to consume.


Agreed -- coding agents / LLMs are definitely imperfect, but it's always hard to contextualize "it failed at X" without knowing exactly what X was (or how the agent was instructed to perform X)


Good point – we’ve definitely noticed a lot more Cloudflare representation these days. That said, there seems to be tiers in terms of the protection they offer (and thus the protection used by the websites in this long-tail), where lower tiers (so far) haven’t required proxies.

Curious if you’ve noticed any particularly well defined, obscure websites? Would love to take a look if so.


Haha I appreciate that! And that’s exactly right. Our goal is to make it so that you don’t have to ask the question “but is it worth the time and effort…” when you want to use or explore a new dataset.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: