{"version":"2.1.257","anchor":"background-auth-snapshot-can-now-carry-a-gateway-token-and","canonical_anchor":"background-auth-snapshot-can-now-carry-a-gateway-token-and","heading":"Background-auth snapshot can now carry a gateway token, and retries on transient read failures","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/background-auth-snapshot-can-now-carry-a-gateway-token-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Background-auth snapshot can now carry a gateway token, and retries on transient read failures\n\nThe startup auth snapshot can carry a gateway token, and a locked-file read failure now retries instead of discarding it.\n\nThe background-auth snapshot consumed at startup can now include a `gatewayToken` field alongside `accessToken`, read via the internal `DCt` consumer. If a snapshot read hits a transient failure (EBUSY, EPERM, or EACCES on Windows), the snapshot env var is no longer deleted or unset immediately; the failure is logged instead and a later read is allowed to retry.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}