{"version":"2.1.246","anchor":"storage-handle-threaded-into-client-creation-and-mcp-calls","canonical_anchor":"storage-handle-threaded-into-client-creation-and-mcp-calls","heading":"Storage handle threaded into client creation and MCP calls","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/storage-handle-threaded-into-client-creation-and-mcp-calls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Storage handle threaded into client creation and MCP calls\n\nCredential access keeps migrating onto one shared handle across client and MCP paths.\n\n**What**\n\nThe API client factory now takes a storage handle and passes it to the pre-request auth refresh and the custom fetch builder, and the headless MCP call path passes it where it used to pass an app-state setter. Continued migration of credential access onto one handle.\n\n**Evidence**\n\n`callMCPToolWithUrlElicitationRetry`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}