{"version":"2.1.238","anchor":"credentials-threaded-alongside-the-storage-handle","canonical_anchor":"credentials-threaded-alongside-the-storage-handle","heading":"Credentials threaded alongside the storage handle","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/credentials-threaded-alongside-the-storage-handle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Credentials threaded alongside the storage handle\n\nCredentials now travel with the storage handle through most call paths, groundwork for per-session logins.\n\n**What**\n\nA credentials value now travels with the existing storage handle through app config, tool-use contexts, artifact and skill call sites, OAuth and gateway login, session title generation and trusted-device enrollment. Several auth reads became asynchronous as a result.\n\n**Details**\n\n- The design OAuth token read now goes through a store read and logs \"Failed to read design OAuth tokens\" when it fails.\n\n**Evidence**\n\n`credentials: r.credentials,`\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}