tengu_mcp_step_up_auth_dialog

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.281, including the newest one read.

Releases whose published page names tengu_mcp_step_up_auth_dialog.

1. v2.1.288 2 Oct 2026
   Dialogs where an MCP server asks you for input can ask you to confirm you are done

   The dialog an MCP server uses to ask you for input can now be told you will confirm when you are done, and can check whether an answer would be taken

   gate cited by this entry

2. v2.1.288 2 Oct 2026
   MCP sign-in now notices when a server asks for more permission

   Claude Code now checks each MCP server sign-in response for a missing-permission answer and returns the server's real response

   gate cited by this entry

3. v2.1.288 2 Oct 2026
   Remote sessions gain steps for repository agents, skills and switching

   Remote sessions have new named setup steps for repository agents, skills, root registration, switches and flag prefetching

   gate cited by this entry

4. v2.1.288 2 Oct 2026
   MCP step-up sign-in dialog now defaults to on

   The dialog for MCP servers that ask you to sign in again with extra permissions now falls back to on when the server sends no setting

   gate cited by this entry

5. v2.1.281 23 Sep 2026
   MCP step-up re-authentication prompt for 403 insufficient_scope (dark-launched)

   Claude Code can offer to sign in to an MCP server again with wider permissions when a tool call is refused for missing scope

   gate cited by this entry, found in this entry's text

6. v2.1.281 23 Sep 2026
   MCP tool calls can ask for consent and re-authenticate when a server returns 403 insufficient_scope (gated off)

   MCP tool calls refused for missing permissions can prompt you to sign in again and retry, behind a gate

   gate cited by this entry, found in this entry's text

Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.

One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.

The earliest release whose published evidence quoted tengu_mcp_step_up_auth_dialog was v2.1.281, 23 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.