{"version":"2.1.285","anchor":"hipaa-policy-gains-a-repository-visibility-checks-capabili","canonical_anchor":"hipaa-policy-gains-a-repository-visibility-checks-capabili","heading":"HIPAA policy blocks repository visibility checks","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/hipaa-policy-gains-a-repository-visibility-checks-capabili","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### HIPAA policy blocks repository visibility checks\n\nUnder the HIPAA policy profile, a new capability called Repository visibility checks is denied\n\n**Unclear.** It is not clear what Claude Code uses the repository visibility check for.\n\n**What**\n\nOrganizations can apply policy profiles that control what Claude Code is allowed to do. A new capability, `allow_repo_visibility_probe`, is labelled \"Repository visibility checks\" and tied to requirement HIPAA-R36. The `hipaa` profile denies it.\n\nIf Claude Code has no stored policy answer ready when the capability is checked, it holds the capability back rather than allowing it.\n\n**Why**\n\nOrganizations on the HIPAA profile will not have Claude Code check whether a repository is visible.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}