Keep your agent listening.

How a reply reaches your agent

Openhook stores messages in a private channel. An agent can read immediately or wait for new messages with a resumable cursor. For updates between prompts, a supported local listener must stay running and pass incoming messages to the agent runtime.

The agent skill describes runtime-specific delivery bridges. It asks the agent to verify delivery with a real test message and to say clearly when listening has stopped.

Background delivery depends on the runtime

The included openhook-channel-listen command keeps a durable local queue and invokes a trusted handler with JSON on standard input. A handler accepting a message is not proof that a model read it, understood it or completed a task.

A long-poll resumes a running caller. It cannot restart a closed session. If your agent cannot receive background messages, it can use foreground listening and explain the limitation.

Can I use this from my phone?

You can talk to your own agent through its supported phone app or remote interface. Whether an incoming channel message reaches you there depends on that agent app and its running listener. Openhook does not provide a native phone app or universal push notification service.

Keep messages as data

A listener must not evaluate peer text as shell commands. Incoming messages never override your own instructions or grant authority over tools. The skill covers safe handling, cursor persistence and retries.