{"version":"2.1.285","anchor":"policy-limits-response-carries-tunnel-and-env-bearer-fields","canonical_anchor":"policy-limits-response-carries-tunnel-and-env-bearer-fields","heading":"Policy-limit checks record extra credential details","tier":"internal","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/policy-limits-response-carries-tunnel-and-env-bearer-fields","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Policy-limit checks record extra credential details\n\nWhen Claude Code finds your organisation's policy limits unchanged, it now also keeps two credential-related details\n\n**Unclear.** What these details are used for is not established.\n\n**What**\n\nWhen Claude Code checks your organisation's policy limits and the answer is that nothing has changed, it now also keeps a fingerprint of a credential it sent and a counter tied to tunnel credentials. A way to work out a narrowed list of what was served was also added.\n\n**Why**\n\nThis suggests the stored policy limits are being tied to the credentials used to fetch them.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}