opencode-hooks

To block dangerous bash commands in OpenCode, configure a PreToolUse hook in your hooks.json file with specific condition patterns that match restricted commands like rm, ensuring safe operation and policy enforcement.

PreToolUse and PostToolUse hooks intercept tool events in OpenCode to block dangerous commands before execution and log tool usage activity after execution, enabling security auditing and governance across the workspace.

Yes, you can enforce security policies and audit tool calls by creating or modifying hooks.json to define hook conditions that intercept, log, and block tool usage based on your specific governance requirements.

Yes, the hook configuration supports debugging and validating hook behavior across common OpenCode tools including bash, edit, and write, allowing you to intercept and log their usage consistently.

The best way to log tool usage activity is by enabling PostToolUse hooks in your hooks.json configuration, which automatically records tool calls and supports ongoing monitoring and audit trail generation.

To validate and debug hook behavior when policies are not applying correctly, review your hook condition patterns in hooks.json and test the PreToolUse and PostToolUse events across common tools like bash and write.