Feature request for product/service
– Other –
Describe the request
A Grok Bot computer can run an always-on process. That process can see new events, write files, and hit HTTPS. It cannot wake the agent chat.
The chat only wakes if I message it, a connected Channel fires, a routine fires, or another agent pings it. There is no way for the computer itself to resume the agent.
Two shapes that would fix it:
A doorbell. A localhost or HTTPS callback the always-on process can POST to, which resumes the chat like an inbound Channel message. One wake per real event, not a polling routine.
A custom harness on the agent’s computer that runs the agent’s process. the computer can keep the harness awake and hand the agent events directly, instead of the chat being a separate thing the computer cannot poke.
Without one of those, anything the computer is watching can only record the event. It cannot get the agent’s attention. This way I am not wasting valuable compute with routines that check if the agent needs to respond.