{"version":"2.1.202","anchor":"unified-credential-error-messages-for-cloud-providers","canonical_anchor":"unified-credential-error-messages-for-cloud-providers","heading":"Unified Credential Error Messages for Cloud Providers","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.202\/e\/unified-credential-error-messages-for-cloud-providers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.202","markdown":"### Unified Credential Error Messages for Cloud Providers\n\nThe separate error strings for each cloud credential provider (Bedrock, Vertex, Foundry, Mantle, Anthropic-on-AWS) have been consolidated into a single generic credential error factory.\n\n**Details**\n\n- All credential providers now use: \"[Provider] credentials are managed by the desktop app, but none are available. The app may have quit or its credential file is stale \u2014 restart the desktop app.\"\n- A new explicit message for incompatible credential types: \"Background agents and teammates are not supported for this credential kind. Run this from the main session, or switch the desktop app to a profile-based or API-key credential. If this is the main session, restart the desktop app.\"\n- AWS credential detection now uses `Pqs()` to read `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_PROFILE`, `AWS_CONFIG_FILE`, and `AWS_SHARED_CREDENTIALS_FILE`\n\n**Evidence**\n\nCredential error factory (search for `\"host-managed provider credentials unavailable\"` and `\"Background agents and teammates are not supported for this credential kind\"`)"}