Hooks

Built-in hooks are described in some older Omnigraph material, but they are not part of the current CLI or server surface. There is no hook command, hook API, or hook configuration format in the current release.

What to use instead

Current Omnigraph coordination patterns use explicit graph state and queries:

1. Represent work state in the graph.
2. Write a query that finds the next work item or condition.
3. Run that query from an agent, scheduler, or review workflow.
4. Write results back on a branch and merge when ready.

This keeps coordination inspectable and versioned even without a built-in event layer.

Example

query pending_reviews() {
    match {
        $t: Ticket { status: "pending" }
        not { $t hasReview $r }
    }
    return { $t.slug, $t.title }
}

An external scheduler or agent runner can execute that query on an interval and start work when rows are returned.