2 ファイル変更 +13 -2
この更新の概要
フック設定におけるok: false（アクションのブロック）を指定した際の動作が、イベント種別ごとに詳細化されました。PreToolUseイベントでブロックした際にツールエラーとしてClaudeへ理由が返され、動作を継続できるよう改善されています。一方で、UserPromptSubmitなどの特定のイベントでは、従来通り警告を表示してターンを終了する仕様であることが明記されました。全体として、自動化プロセスにおけるエラーハンドリングと継続性の制御がより緻密に定義されています。
@@ -688,7 +688,10 @@ For decisions that require judgment rather than deterministic rules, use `type:
The model's only job is to return a yes/no decision as JSON:
- `"ok": true`: the action proceeds
- `"ok": false`: the action is blocked. For `Stop` and `SubagentStop` hooks, the `reason` is fed back to Claude so it keeps working. For other events, the turn ends and the `reason` appears in the chat as a warning line. Claude does not see it.
- `"ok": false`: what happens depends on the event:
- `Stop` and `SubagentStop`: the `reason` is fed back to Claude so it keeps working
- `PreToolUse`: the tool call is denied and the `reason` is returned to Claude as the tool error, so it can adjust and continue
- `PostToolUse`, `PostToolBatch`, `UserPromptSubmit`, and `UserPromptExpansion`: the turn ends and the `reason` appears in the chat as a warning line
This example uses a `Stop` hook to ask the model whether all requested tasks are complete. If the model returns `"ok": false`, Claude keeps working and uses the `reason` as its next instruction:
@@ -2358,7 +2358,15 @@ The LLM must respond with JSON containing:
| `ok` | `true` allows the action, `false` blocks it |
| `reason` | Required when `ok` is `false`. Explanation for the block |
For `Stop` and `SubagentStop`, an `ok: false` reason is fed back to Claude as its next instruction and the turn continues. For all other supported events, the turn ends and the reason appears in the chat as a warning line; Claude does not see it. This is equivalent to returning `"continue": false` from a command hook. If you need different blocking semantics on those events, use a [command hook](#command-hook-fields) with the per-event fields described in [Decision control](#decision-control).
What happens on `ok: false` depends on the event:
- `Stop` and `SubagentStop`: the reason is fed back to Claude as its next instruction and the turn continues
- `PreToolUse`: the tool call is denied and the reason is returned to Claude as the tool error, equivalent to a command hook's `permissionDecision: "deny"`
- `PostToolUse`, `PostToolBatch`, `UserPromptSubmit`, and `UserPromptExpansion`: the turn ends and the reason appears in the chat as a warning line, equivalent to returning `"continue": false` from a command hook
- `PostToolUseFailure`, `TaskCreated`, and `TaskCompleted`: the reason is returned to Claude as a tool error, similar to `PreToolUse`
- `PermissionRequest`: `ok: false` has no effect. To deny an approval from a hook, use a [command hook](#command-hook-fields) returning `hookSpecificOutput.decision.behavior: "deny"`
If you need finer control on any event, use a [command hook](#command-hook-fields) with the per-event fields described in [Decision control](#decision-control).
### Example: Multi-criteria Stop hook