Ir al contenido
#0024
PipeAgentNotifications

Tail your agent on the train, get pinged when it lands

You kicked off a long-running agent before leaving the office. Forty-minute task, give or take. You're on the train. You don't want to babysit, but you want to glance.

The agent streams its trace to a pipe path. On your phone, you curl ?progress in a terminal app and watch state messages drift by: streaming..., tool: web_search, tool: file_write. You don't read every word. You just want to know it's alive.

When the agent's outer loop finishes, its last act is to hit hoody-notifications. Your phone buzzes. You open the same pipe URL on your phone in a browser; the final output is rendered inline, served by the pipe service itself.

Two URLs and a buzz. No SDK, no client app, no dashboard. The agent runs on a server. The status lives on your phone.

Your phone is the agent's status bar.