{"version":"2.1.259","anchor":"session-identity-now-cached-per-host-and-derived-from-a-new","canonical_anchor":"session-identity-now-cached-per-host-and-derived-from-a-new","heading":"Session identity now cached per host and derived from a new token source","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/session-identity-now-cached-per-host-and-derived-from-a-new","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Session identity now cached per host and derived from a new token source\n\nRemote session identity is now cached per host and read through a helper instead of the access-token variable directly.\n\nThe remote-session identity resolver, which derives `organizationUuid`, `accountUuid`, and `emailAddress`, now caches its result per host and reads its token through a new internal helper instead of reading `CLAUDE_CODE_SESSION_ACCESS_TOKEN` directly. This avoids repeated JWT parsing when the token hasn't changed.\n\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_SESSION_ACCESS_TOKEN`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}