{"version":"2.1.257","anchor":"new-user-facing-errors-for-cloud-session-sync-and-tls-pinnin","canonical_anchor":"new-user-facing-errors-for-cloud-session-sync-and-tls-pinnin","heading":"New user-facing errors for cloud session sync and TLS pinning failures","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-user-facing-errors-for-cloud-session-sync-and-tls-pinnin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New user-facing errors for cloud session sync and TLS pinning failures\n\nNew messages cover sync being switched off because settings.json could not be parsed, and sign-in aborting on a changed TLS certificate.\n\nTwo new error\/status messages are now shown to users. One appears when file sync is turned off for a session because the checkout's `.claude\/settings.json` or `settings.local.json` cannot be read or parsed. The other aborts sign-in when a gateway's TLS certificate unexpectedly changes mid-flow.\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}