{"version":"2.1.292","anchor":"session-init-result-caching-fix-in-the-sdk-control-surface","canonical_anchor":"session-init-result-caching-fix-in-the-sdk-control-surface","heading":"SDK session setup and account calls read from a different stored value","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/session-init-result-caching-fix-in-the-sdk-control-surface","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### SDK session setup and account calls read from a different stored value\n\nIn the SDK, the calls that return session setup results, account information and turn count now read from a different stored value\n\n**Unclear.** It is not stated whether the account details or setup results that SDK programs receive are actually different now.\n\n**What**\n\nThe SDK is the library that lets other programs run Claude Code. Three things it returns now come from a different stored value inside Claude Code than before:\n\n- the result of setting up the session\n\n- the account information\n\n- the turn count\n\n**Why**\n\nThis could change which account details programs built on the SDK receive.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}