{"version":"2.1.239","anchor":"oauth-refresh-now-takes-the-credential-store-as-an-argument","canonical_anchor":"oauth-refresh-now-takes-the-credential-store-as-an-argument","heading":"OAuth refresh now takes the credential store as an argument","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/oauth-refresh-now-takes-the-credential-store-as-an-argument","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### OAuth refresh now takes the credential store as an argument\n\nToken refresh now receives the credential store instead of looking it up, and de-duplicates by store type.\n\n**What**\n\nThe token refresh entry point accepts the credential store and storage handle rather than looking them up, and de-duplicates concurrent refreshes separately for bare credentials versus store-backed ones. The store module existed before but was mostly reached ambiently.\n\n**Details**\n\n- The same value now rides through request options objects, tool-use contexts, agent and query options, MCP login and logout handlers, UI contexts, and bridge\/cowork session creation and background-exit paths.\n- This is why so many function signatures grew a trailing argument in this build.\n\n**Evidence**\n\n`tryCreateCredentialsStore`\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}