{"version":"2.1.277","anchor":"projects-tools-org-policy-disabled-message-is-now-dynamic","canonical_anchor":"projects-tools-org-policy-disabled-message-is-now-dynamic","heading":"Projects tool's org-policy-disabled message is now dynamic, and Projects context is retried after a policy cache miss","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/projects-tools-org-policy-disabled-message-is-now-dynamic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Projects tool's org-policy-disabled message is now dynamic, and Projects context is retried after a policy cache miss\n\nProjects-disabled-by-policy message is now dynamic, and access retries after policy resolves\n\n**What**\n\nThe fixed message telling you \"Projects is disabled by your organization's policy\" has been replaced with dynamic wording driven by the `allow_projects_tool` policy check, so the text now matches whatever the actual policy decision says. Separately, if the policy check for `allow_projects_tool` was previously unresolved (a cache miss) and later resolves to allowed, Claude Code now automatically re-subscribes and rebuilds your project context instead of requiring a restart.\n\n**Why**\n\nThis means the message you see about Projects being disabled will more accurately reflect your organization's actual policy, and access to Projects can recover on its own once the policy check catches up, without you needing to do anything.\n\n- Area: Elsewhere\n- Names: `allow_projects_tool`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}