{"version":"2.1.232","anchor":"requests-now-declare-that-they-need-a-claude-ai-login-specif","canonical_anchor":"requests-now-declare-that-they-need-a-claude-ai-login-specif","heading":"Requests now declare that they need a claude.ai login specifically","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/requests-now-declare-that-they-need-a-claude-ai-login-specif","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Requests now declare that they need a claude.ai login specifically\n\nSome internal endpoints now demand a claude.ai login specifically and fail with their own message.\n\n**What**\n\nInternal endpoints that previously declared their auth requirement as \"required\" now declare `claude-ai-oauth`, and the request layer gained a branch that checks for a claude.ai login in particular, fails with its own detail string when there is none, and adds an `anthropic-beta` header. The old generic value no longer appears anywhere.\n\n**Details**\n\n- Affected call sites include the artifacts and frame endpoints and artifact unsubscribe.\n\n**Evidence**\n\n`detail: \"no claude.ai login\"`\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}