Struct HookExecutor 

pub struct HookExecutor { /* private fields */ }

Executes hook commands in response to agent lifecycle events.

Implementations

impl HookExecutor

pub fn new(hooks: Vec<HookConfig>) -> Self

Create an executor with the given hook configurations.

pub fn empty() -> Self

Create an executor with no hooks (a no-op executor).

pub fn has_hooks(&self) -> bool

Whether any hooks are configured.

pub async fn run_pre_tool_use( &self, tool_name: &str, ctx: &HookContext, ) -> PreHookResult

Run all matching PreToolUse hooks and return the aggregate result.

If any hook returns Block, the overall result is Block. If any hook returns Modify, the last Modify wins. If a hook times out, crashes, or produces non-JSON output, it degrades to Allow (the tool call is not disrupted).

pub async fn run_post_tool_use(&self, tool_name: &str, ctx: &HookContext)

Run all matching PostToolUse hooks (fire-and-forget).

Errors are silently swallowed — post-hooks are advisory.

pub async fn run_user_prompt_submit( &self, prompt: &str, session_id: &str, cwd: &str, ) -> UserPromptHookResult

Run every UserPromptSubmit hook in registration order. Aggregates results following CC’s contract:

• Any hook returning decision: "block" (or exit non-zero) → the whole prompt is blocked; first reason wins.
• Hooks emitting hookSpecificOutput.additionalContext (JSON) or plain text on stdout → concatenated and surfaced to the agent as extra context to append to the user message.
• Empty stdout / unparseable JSON → treated as a silent continue, so a hook author can still print(...) debug noise without accidentally injecting it into every prompt.

Each hook receives the payload as JSON on stdin (CC parity), so scripts using json.load(sys.stdin) work unchanged.

pub async fn run_session_event(&self, event: HookEvent, ctx: &HookContext)

Run all hooks matching a session-level event (fire-and-forget).

pub async fn execute_hook( &self, hook: &HookConfig, ctx: &HookContext, ) -> Result<String>

Execute a single hook command and return its stdout.

The hook receives context via environment variables:

• ATOMCODE_HOOK_EVENT — the event name (e.g. pre_tool_use)
• ATOMCODE_TOOL_NAME — tool name, if applicable
• ATOMCODE_HOOK_CONTEXT — full JSON-serialized HookContext

The command is killed after hook.timeout_ms milliseconds.