MCP (Model Context Protocol) servers connect Claude Code to outside tools and services. Such a server can ask you for information through an elicitation, a dialog that pauses and asks you to respond.
The elicitation dialog now receives two more pieces of information:
- whether the server expects you to confirm that you have finished
- a way to check whether an answer would be accepted
Previously it was given only the server's name, the request and a way to send your response.
This prepares the dialog for requests where you complete a step and then confirm it, rather than only typing an answer.
tengu_mcp_step_up_auth_dialog On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.288: on
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.288. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not established whether this dialog is linked to the step-up sign-in setting for MCP servers whose default changed.