{"version":"2.1.288","anchor":"plugin-install-policy-message-no-longer-mentions-non-anthrop","canonical_anchor":"plugin-install-policy-message-no-longer-mentions-non-anthrop","heading":"Plugin install error no longer mentions needing a direct Anthropic connection","tier":"notice","area":"Plugins","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/plugin-install-policy-message-no-longer-mentions-non-anthrop","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Plugin install error no longer mentions needing a direct Anthropic connection\n\nThe cannot-install message for blocked plugins no longer says you need a direct Anthropic API connection, and always says the plugin is unavailable\n\n**Unclear.** It is not clear whether the requirement itself was removed or only the wording about it.\n\n**What**\n\nWhen a plugin cannot be installed because of a policy, the message used to say in one case that it needed a direct Anthropic API connection (not Bedrock, Vertex or a gateway) with non-essential network traffic allowed. That wording is gone. The message now always says the plugin is unavailable, followed by the reason.\n\n**Why**\n\nIf you saw the old connection advice before, it no longer appears. The message alone does not tell you whether the connection requirement still applies.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}