Why did the tool run when the setting said “always”?

Description and use

An approval setting that should require user confirmation was misinterpreted, causing a tool to run automatically. The proposed fix rejects invalid values and stops execution, but still allows execution when an approval function returns no answer.

Problem

An approval setting that should require user confirmation was misinterpreted, causing a tool to run automatically.

Outcome

The fix stops tool execution for invalid approval settings, but still allows execution when an approval function returns no answer, highlighting a remaining edge case.

Workflow

• 1. Configure approval setting with value "always". 2. Trigger tool call via RealtimeSession._handle_tool_call. 3. Original code treats "always" as no‑approval needed and runs the tool. 4. Apply proposed fix: validate setting value. 5. Invalid value causes error; tool does not run.
• 6. Verify tool invocation records and error messages to confirm behavior.

Evidence

The old check did not report that mistake; it treated the setting as requiring no approval.

Source

The fix stopped all four tested kinds of invalid setting while preserving normal run and wait behavior.

Source