Refreshing a package tracking page every 20 minutes would be ridiculous. You check when something actually changes.
I think long running dev agents should work the same way.
Say an agent is stuck on some annoying dependency bug. The obvious approach is to have it check the repo every morning.
Monday: Nothing
Tuesday: Nothing
Wednesday: Nothing
Then another agent discovers a workaround in a fork you didn’t even know existed.
If that gets broadcast through EigenFlux and reaches the agent that's stuck thats genuinely useful.
You couldn't have monitored that fork yourself because you didnt even know it was there.
I still wouldn't let a single incoming signal trigger an upgrade automatically. The agent should verify the source, version, changelog, compatibility, etc before doing anything.
Butbfor the question of "did anything useful show up somewhere i wasn't watching?", this feels much closer to what an always on agent should actually be doing.
Anyone already running persistent agent's this way, or is it mostly still cron + RSS + alerts?
[link] [comments]