{"version":"2.1.302","anchor":"project-mcp-approval-dialog-and-managed-settings-errors-form","canonical_anchor":"project-mcp-approval-dialog-and-managed-settings-errors-form","heading":"Settings file paths in the MCP approval dialog and settings errors are now formatted","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/project-mcp-approval-dialog-and-managed-settings-errors-form","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Settings file paths in the MCP approval dialog and settings errors are now formatted\n\nThe project MCP approval dialog and managed-settings errors now tidy a file's path before showing it, rather than showing it raw\n\n**What**\n\nTwo places now pass a settings file's path through a formatting step before showing it, instead of showing the raw value:\n\n- the dialog that asks you to approve MCP servers set up for a project (MCP is how Claude Code connects to outside tools)\n\n- error messages about managed settings, the settings an organisation sets for everyone\n\nWhen no file is known, the errors still say \"managed settings\".\n\n**Why**\n\nFile paths in these dialogs and errors may look different from before.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}