Struct ConfirmationConfig 

pub struct ConfirmationConfig {
    pub tool_patterns: Vec<String>,
    pub session_id: String,
    pub register: RegisterConfirmation,
    pub clear: ClearConfirmation,
}

Hooks the runner needs to wire write-confirmation HITL into a turn without depending on AppState directly (keeps the runner unit-testable).

When Some, the runner installs a core ConfirmationHook over every tool whose name matches one of tool_patterns. When such a tool is about to run, the agent loop parks inside the hook’s pre_call and emits a HumanRequest::Confirm; the runner’s bridge:

1. calls register with the session’s HumanResponse sender, so a later confirm_tool_action can resume,
2. emits a confirm_tool_action_required event through the turn sink.

On confirm_tool_action, the handler feeds the sender HumanResponse and the parked tool either executes (approved) or is skipped with a rejection result (denied). None (the default) installs no hook → no tool ever parks → behavior is byte-for-byte identical to before HITL.

Fields

tool_patterns: Vec<String>

Tool-name substrings that require human approval (matched by core’s ConfirmationHook, which uses contains matching). Empty disables HITL.

session_id: String

The session this turn belongs to — carried on the confirm_tool_action_required event and the registration key so the inbound confirm_tool_action (keyed by sessionId) routes back here.

register: RegisterConfirmation

Registers the parked turn’s HumanResponse sender under session_id (typically AppState::register_confirmation).

clear: ClearConfirmation

Clears any registered sender for session_id when the turn ends (typically AppState::clear_confirmation), so a stale sender can’t mis-route a later confirmation.