{"version":"2.1.118","anchor":"posttoolbatch-hook-event","canonical_anchor":"posttoolbatch-hook-event","heading":"PostToolBatch Hook Event","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.118\/e\/posttoolbatch-hook-event","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.118","markdown":"### PostToolBatch Hook Event\n\n**What**\n\nA new hook event type that fires once after every tool call in a batch has resolved, before the next model request.\n\n**Details**\n\n- Unlike `PostToolUse` which fires per-tool and may run concurrently for parallel tool calls, `PostToolBatch` fires exactly once with the full batch\n- Hook input includes `tool_calls` array with `{tool_name, tool_input, tool_use_id, tool_response}` for each call\n- Supports `additionalContext` return to inject content into the next model request\n- Can return `\"stopAgent\": true` to halt execution, showing `\"Execution stopped by PostToolBatch hook\"`\n- Available in hooks configuration under the event name `\"PostToolBatch\"`\n\n**Evidence**\n\nSchema definition (search for `\"PostToolBatch\"`) at line ~263664. Hook input schema describes `\"Fired once after every tool call in a batch has resolved, before the next model request\"`."}