{"version":"2.1.310","anchor":"startup-reads-signature-facts-and-exits-on-plugin-flag-confl","canonical_anchor":"startup-reads-signature-facts-and-exits-on-plugin-flag-confl","heading":"Remote managed settings setup now reads signature details","tier":"internal","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/startup-reads-signature-facts-and-exits-on-plugin-flag-confl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Remote managed settings setup now reads signature details\n\nWhen setting up remote managed settings at startup, Claude Code now reads signature details alongside the policy and settings\n\n**What**\n\nRemote managed settings are settings an organization sends to Claude Code from a server. When Claude Code sets them up at startup, it now reads signature details as well as the policy and the settings themselves. Previously it did not.\n\nThe startup check on plugin flags works as before. In a guarded mode, Claude Code still refuses `--plugin-dir`, `--plugin-dir-no-mcp`, `--plugin-url` and `--agents` when plugins are also given inline through `CLAUDE_CODE_PLUGIN_DIRS`.\n\n**Why**\n\nChecking remote managed settings now takes an extra piece of information about their signature, the mark that shows they are genuine.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}