Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.274,
ImprovementsSection of the release
Unclear What condition the new Nk(s) check actually verifies is not specified.
What
The fetch wrapper that retries a request after a 403 response with a sent bearer token now also requires a new check (Nk) to pass, in addition to the existing check that the response was a 403 with a token sent.
The same check now gates whether a 403 response gets turned into a needs_consent design-MCP error, restricting that behavior to first-party design MCP endpoints.
Why
This narrows when the 403-retry and design-consent behavior kicks in, preventing them from firing for responses that aren't actually from the first-party design MCP service.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat condition the new Nk(s) check actually verifies is not specified.
