{"version":"2.1.285","anchor":"policy-limits-reacts-to-ssh-launcher-credential-changes","canonical_anchor":"policy-limits-reacts-to-ssh-launcher-credential-changes","heading":"Organization policy limits recheck when the claude ssh credential changes","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/policy-limits-reacts-to-ssh-launcher-credential-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Organization policy limits recheck when the `claude ssh` credential changes\n\nPolicy limits now refetch or hold back some settings when the credential supplied by the `claude ssh` launcher changes\n\n**What**\n\nPolicy limits are restrictions your organization sets on what Claude Code may do. When you connect through the `claude ssh` launcher, the launcher supplies a credential, which is the login proof Claude Code sends to the server. Claude Code now notices when that credential changes. When it does, Claude Code either fetches the policy again or holds back settings that apply only on your machine.\n\nClaude Code also reloads the policy when the credential set in the environment is no longer the one actually being sent.\n\n**Why**\n\nThis keeps your organization's policy matched to the account a remote session is really using, so limits fetched under one credential are not applied under another.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}