Under the hood
No documentation found
Strict tool-result pairing mode is now controlled by the client's launch options, not an experiment gate
What
The setting that decides whether Claude Code throws an error (instead of silently repairing) when tool calls and their results don't line up correctly has moved to a different check. It's now read from host.launchOptions.strictToolResultPairing(), a value the client application provides at launch, rather than from an internal experiment flag.
Why
This puts control of strict pairing behavior in the hands of whatever application is embedding Claude Code, rather than in a centrally managed experiment.
Names in the bundlestrictToolResultPairing