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.210: 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.210. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When an MCP connector returns a new -32003 needs_approval error code, Claude Code now surfaces a retroactive approval card instead of propagating the error. The user can approve or deny the call from within the normal permission flow.
- Previously,
-32003responses would surface as raw errors. Now they trigger a consent prompt with the connector name and a description of the required action. - If the user approves, the call is automatically retried; if they deny, an informative
"Approval denied for <connector>"error is returned to the model. - Approval is surfaced as an
"approval card"in the UI with the message"This connector call requires your approval to proceed.". - The feature is controlled by
tengu_mcp_proxy_needs_approval_retry(default enabled). - If the approval was conditioned on edited arguments (which cannot safely be replayed), the tool raises a clear error:
"The approval for X was conditioned on edited arguments, which can't be applied on this retroactive card".
Error code constant (search for "-32003") and approval message (search for "connector requires approval for this call")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.