{"version":"2.1.305","anchor":"pointerless-mcp-elicitation-consent-prompt-behind-claude-cod","canonical_anchor":"pointerless-mcp-elicitation-consent-prompt-behind-claude-cod","heading":"MCP question dialogs know which plugin asked, with an optional no-preselection mode","tier":"use","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/pointerless-mcp-elicitation-consent-prompt-behind-claude-cod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### MCP question dialogs know which plugin asked, with an optional no-preselection mode\n\nMCP elicitation dialogs now receive the plugin source, and CLAUDE_CODE_CONSENT_POINTERLESS can stop Accept being preselected\n\n**Unclear.** Which servers and plugins pass the extra check, so it is unclear whether setting the variable changes every MCP dialog.\n\n**What**\n\nAn MCP server (a connected tool provider) can ask you for input or approval through a dialog, called an elicitation.\n\n- The MCP client now passes `pluginSource` from the server's config, and the dialog receives it, so it can tell which plugin the server came from. It uses a plugin-specific title when one is available.\n\n- With the environment variable `CLAUDE_CODE_CONSENT_POINTERLESS` set and a further condition met, neither Accept nor Decline is preselected. The dialog shows \"(press an arrow key to choose)\" and Enter does nothing until you pick a button. Before, Accept was preselected when the form had no fields.\n\n- Typing in the dialog is now tracked.\n\n**Why**\n\nKnowing the plugin behind a request helps you judge it, and the optional mode stops a stray Enter from accepting something by accident. That mode does nothing unless the variable is set.\n\n- Area: MCP\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}