{"version":"2.1.223","anchor":"clearer-failures-when-claude-ai-project-scopes-can-t-be-obta","canonical_anchor":"clearer-failures-when-claude-ai-project-scopes-can-t-be-obta","heading":"Clearer failures when claude.ai project scopes can't be obtained","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/clearer-failures-when-claude-ai-project-scopes-can-t-be-obta","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Clearer failures when claude.ai project scopes can't be obtained\n\nWhen project permissions fail, you now get a specific reason and advice instead of a vague error.\n\n**What**\n\nThe project-scope error mapper gained two new reasons and broadened an existing one, so the message tells you which situation you are in.\n\n**Details**\n\n- `custom_client`: a custom OAuth client cannot be granted project scopes\n- `save_failed`: refreshed credentials could not be stored because secure storage was unavailable, and the server has already consumed the old ones, so the advice is to run `\/login` and retry\n- `no_refresh` now covers expired or revoked refresh tokens generally, not just `CLAUDE_CODE_OAUTH_TOKEN`\n\n**Evidence**\n\n`Could not save the refreshed claude.ai credentials (secure storage was unavailable), and the server has already consumed the stored ones. Run \/login to reconnect, then retry.`\n\n- Area: Auth\n- Names: `\/login`, `CLAUDE_CODE_OAUTH_TOKEN`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}