Documentation
¶
Overview ¶
Package hooks provides an event-based hook system for cross-cutting concerns.
Instead of individual callback fields on the executor, hooks allow multiple listeners to subscribe to events at various points in the execution lifecycle. This follows the middleware pattern from web frameworks: logging, telemetry, metrics, and other concerns register as hooks without modifying core logic.
Index ¶
Constants ¶
View Source
const ( GoalStart = "goal.start" GoalComplete = "goal.complete" ToolCall = "tool.call" ToolError = "tool.error" LLMError = "llm.error" SkillLoaded = "skill.loaded" MCPToolCall = "mcp.tool.call" SubAgentStart = "subagent.start" SubAgentComplete = "subagent.complete" SupervisionEvent = "supervision.event" )
Standard event types for the execution lifecycle.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Registry ¶
type Registry struct {
// contains filtered or unexported fields
}
Registry holds hooks organized by event type. It is safe for concurrent use.
Click to show internal directories.
Click to hide internal directories.