Skip to the content.

English · 中文

Put agents on your production signals without handing them the keys.

A signal comes in: an alert, a chat message, a ticket, a timer. A pipe signs, routes and prices it. An agent investigates it read-only, and proves it is read-only at startup. The report reaches a person as a card they can rule on. Nothing touches production without a signed press.

service what it does
hookrelay The pipe. Adapts any webhook, routes it, delivers to chat, and keeps one ledger of every hop.
hookjudge The judge. Decides cheaply whether a person must act now. Most events never pay for a model.
hookprobe The investigator. One read-only agent run per event, behind an OpenClaw-compatible HTTP contract. It also runs on its own.

The investigator is the product. The pipe and the judge are the smallest alerting front end for a team that has none. One deployment is one team: this is not a work-management platform, a multi-tenant SaaS or an agent framework.

Start here

hookprobe's console: a real investigation, conclusion first, the root cause it could not establish said so, and the bill under it

The three boards read in Chinese or English and follow the system’s light or dark; the full tour has every screenshot, from local runs and not mockups.

How it fits together

upstreams ──► hookrelay ──► hookjudge ──► hookrelay ──► chat bridge / webhook
                  │
                  └──► hookprobe ──► hookrelay ──► the same channels
                       (critical/high; a rehearsal until it has a model)

The same pipe also carries an operator’s own work signals to a planner and, on a person’s press, to a work runner (two deployment shapes, one codebase).

Read more

MIT licensed.