Retrying MCP calls that need approval now uses one shared rule, so behaviour is consistent.
tengu_mcp_proxy_needs_approval_retry Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.221: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.221. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The condition that decides whether a -32003 needs_approval response should be retried is now one predicate shared by both places that used it.
- The predicate covers the error code, presence of args_sha256 in data, the retry not yet being used, and the gate check.
- It is reused by the isExpectedError classifier and by the retry branch.
- The tool name interpolated into the log line is type-checked before use instead of being read off an untyped object.
- Gated on
tengu_mcp_proxy_needs_approval_retrywith fallback true.
tengu_mcp_proxy_needs_approval_retry
Strings lifted out of the shipped bundle, so the claim above can be checked against them.