Back to Signal Feed
ProductionTracked since May 22, 2026

Added pre/post execution hooks with PreToolUse denial for tool calls

Goose v1.35.0 introduced a new tool-execution hooks system with PreToolUse denial support, enabling custom logic to run before and after each tool call and block disallowed actions before they execute.

Goose tool executionpre/post hooksPreToolUse denial hookACP tool runtime

What Happened

  • Goose v1.35.0 introduced a new tool-execution hooks system with PreToolUse denial support, enabling custom logic to run before and after each tool call and block disallowed actions before they execute.
  • Goose v1.35.0 introduced a new tool-execution hooks system with PreToolUse denial support, enabling custom logic to run before and after each tool call and block disallowed actions before they execute.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

The release adds a concrete extensibility layer in the tool runtime: developers can register hook logic around tool calls and a PreToolUse denial hook to enforce policy decisions at execution time.

Why Track This

Why It Matters

Developers and operators can now intercept tool calls before execution, so risky or policy-violating actions are more likely to be prevented instead of happening unexpectedly in active agent sessions. This is implemented via a new extensible pre/post tool execution hook pipeline and dedicated PreToolUse denial support, which should reduce unsafe automation fallout; watch for hook failures, ordering/precedence interactions, and whether denial paths surface clear user-visible diagnostics so legitimate workflows are not accidentally blocked.

Impact

Developers and operators can now intercept tool calls before execution, so risky or policy-violating actions are more likely to be prevented instead of happening unexpectedly in active agent sessions. This is implemented via a new extensible pre/post tool execution hook pipeline and dedicated PreToolUse denial support, which should reduce unsafe automation fallout; watch for hook failures, ordering/precedence interactions, and whether denial paths surface clear user-visible diagnostics so legitimate workflows are not accidentally blocked.

What To Watch Next

  • Watch whether Goose tool execution becomes a repeated pattern.
  • Track follow-up changes around AI Code Review.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: misconfigured_hooks_block_critical_tools, hook_errors_mask_root_cause_of_tool_failures.
Open Topic TimelineOpen Technical EventOpen Original Sourcemisconfigured_hooks_block_critical_tools / hook_errors_mask_root_cause_of_tool_failures / insufficient_visibility_into_denied_tool_calls

Supporting Evidence