Agent Hook

How it works in practice

A team wires an agent hook to their main branch: every merge fires the dependency⛓️DependencyTeam & OrganisationA cross-team or system dependencyView reference →-audit agent. The hook carries the event (push to main), the condition (changed files include package.json), and the target (the agent definition to wake). On merge, the hook triggers the continuous-integration pipeline, which runs the agent inside it; the agent checks for newly vulnerable dependencies and comments on the next pull request if it finds any. A second hook on a nightly schedule fires the same definition against the full tree, so the agent runs both reactively and on a cadence from one shared configuration.

Agent hook vs. its neighbours

• Agent definition is the agent the hook wakes. The hook holds no instructions and no tools; it holds an event and a pointer. One definition can have several hooks, and one hook fires one definition.
• CI pipeline🚇CI PipelineDevOps & PlatformA CI/CD pipelineView reference → is automation triggered by code events, often the very thing a hook fires into. The hook is the trigger and routing layer; the pipeline is the execution environment it can hand the agent to.
• Workflow run⏯️Workflow RunWorkflows & AgentsAn execution of a workflowView reference → is a single execution of a workflow, during which a hook may fire mid-stream. The hook is the cause; the run is the context the firing happens inside.

In the graph

In the Unified Product Graph, an agent hook sits in the automation region as the trigger primitive. It connects to its agent through agent_definition_triggered_via_agent_hookAgent Definitiontriggered viaAgent Hookhierarchy, and it reaches outward into the rest of the automation surface: agent_hook_triggers_ci_pipelineAgent HooktriggersCI Pipelinecross-domain ties it to a ci_pipeline🚇CI PipelineDevOps & PlatformA CI/CD pipelineView reference →, and agent_hook_fires_during_workflow_runAgent Hookfires duringWorkflow Runcausal records when a hook fired inside a live workflow_run⏯️Workflow RunWorkflows & AgentsAn execution of a workflowView reference →. Separating the trigger from the agent it fires means the same agent can be reached by many events, and a single event can be traced to every agent it wakes, so the question "what set this agent off, and when?" is answerable from the graph alone.