{"version":"2.1.246","anchor":"credentials-and-storage-handles-passed-explicitly-instead-of","canonical_anchor":"credentials-and-storage-handles-passed-explicitly-instead-of","heading":"Credentials and storage handles passed explicitly instead of read from ambient state","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/credentials-and-storage-handles-passed-explicitly-instead-of","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Credentials and storage handles passed explicitly instead of read from ambient state\n\nCredentials and storage are passed explicitly rather than read from ambient state.\n\n**What**\n\nAPI key verification, model-config fetching, the network-permission classifier and several resume and print helpers now take credentials and a storage handle as arguments. Worker startup and the Chrome MCP server prime credentials, cached managed settings and a stored login copy before running.\n\n**Details**\n\n- On Windows, the credential-manager storage backend is selected only when the cached remote flag `tengu_windows_credman` is true, so it stays off unless that flag is set.\n\n**Evidence**\n\n`api_key_verify`\n\n- Flag `tengu_windows_credman`: Off in both readings (read for one account on one subscription tier against v2.1.246; this account: off, anonymous baseline: off, compiled default: not a boolean we can read)\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}