{"version":"2.1.285","anchor":"plugin-network-policy-message-now-assembled-via-a-shared-hel","canonical_anchor":"plugin-network-policy-message-now-assembled-via-a-shared-hel","heading":"The message about blocked plugin network access is now built differently","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/plugin-network-policy-message-now-assembled-via-a-shared-hel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### The message about blocked plugin network access is now built differently\n\nThe notice that plugins cannot use the network is now put together from a shared policy check instead of a fixed sentence\n\n**Unclear.** What the shared check looks at, and the full wording of the new message, are not clear.\n\n**What**\n\nWhen plugins are not allowed to use the network, Claude Code used to show the fixed message \"network access from plugins is disabled by policy\". The message now starts with \"Network access from plugins is\" and the rest comes from a shared check of your policy. The separate message \"nonessential network traffic is disabled for this session\" is unchanged.\n\n**Why**\n\nThe decision about plugin network access may now go through a different policy check than before.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}