Comment by what
2 days ago
Maybe I’m out of touch but why do you need an LLM to decide if there’s any work to be done? Can’t it just queue or schedule tasks? We already have technology for that that doesn’t require an LLM.
2 days ago
Maybe I’m out of touch but why do you need an LLM to decide if there’s any work to be done? Can’t it just queue or schedule tasks? We already have technology for that that doesn’t require an LLM.
Tasks might have prerequisites or conditions.
Like "if it's raining, remind me to grab my umbrella before I leave for work"
-> "is it raining?" requires a tool call to a weather service
-> "before I leave for work" needs access to the user's calendar and information when they leave compared to the time their work day starts
-> "remind me" needs a way to communicate to the user in an efficient way, Telegram, iMessage or Whatsapp for example.
Totally valid for fixed, well-defined tasks — a cron job is cheaper and more reliable there. The LLM earns its keep when the heartbeat involves contextual judgment: not just "is there a task in the queue" but "given everything happening right now, what actually matters?" If the agent needs to reason about priority, relevance, or context before deciding what to surface — that's where the local model pulls its weight. If your agents only do fixed tasks, you're totally right, you don't need it!