A hook reacts to something happening in Coroid. You choose an event, write instructions in plain language, and the hook runs when the event fires.
Find them under Settings → Automation → Automations.
Events you can react to
| Category | Examples |
|---|---|
| Task | Created, status changed, phase changed, completed, failed |
| Agent | Started, iteration, tool called, completed, error |
| Repository | Commit pushed, branch created, pull request opened, pull request merged |
| Analysis | Dependency found, security issue, analysis completed |
| Sync | External source updated |
| Deploy | Started, completed, failed |
Read-only by default
Hooks analyse and report. They can create follow-up work; they do not modify your code directly.
That default is what makes them safe to adopt. An automation that edits code in response to an event is acting at the moment least likely to be supervised. A hook that opens a task produces the same outcome through the normal path — specification, plan, verification, review, pull request.
Writing good instructions
Hook instructions are processed by a model, so they read like instructions to a colleague rather than code. The quality bar is the same as for a specification: say what to look at, what matters, and what to do.
Be specific about the "do nothing" case. Without it, a hook will find something to say every time it runs, and hooks that always fire are hooks people stop reading.
Guardrails
Three protections exist because event-driven automation fails in predictable ways:
Rate limits. Per minute, per hour and per day, configurable per hook. A hook on a high-frequency event can otherwise fire hundreds of times during a busy merge.
Chain depth. Hooks can trigger events that trigger hooks. A maximum chain depth stops that becoming a loop.
Tool permissions. What a hook may reach is controlled — read-only access, MCP calls and task creation are separately governed.
Permissions
Hook management is admin-only; all members can see hooks and their execution history. Given a hook runs with organization-level reach, that asymmetry is deliberate.
Watching them
Each hook keeps a delivery log and analytics. Check the log after enabling a new hook — the failure mode is not an error, it is firing constantly and producing nothing anyone acts on.
Hooks, schedules and Sentinel
| Mechanism | Triggered by |
|---|---|
| Hook | A platform event |
| Schedule | Time |
| Sentinel | A condition being observed |