{"version":"2.1.232","anchor":"artifact-auth-errors-say-which-login-is-needed","canonical_anchor":"artifact-auth-errors-say-which-login-is-needed","heading":"Artifact auth errors say which login is needed","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/artifact-auth-errors-say-which-login-is-needed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Artifact auth errors say which login is needed\n\nArtifact auth errors now tell you a claude.ai login is needed and to run \/logout to clear an API key.\n\n**What**\n\nWhen artifact publishing fails because the session is signed in the wrong way, the error now says artifacts need a claude.ai login, and if a Console API key was saved by an earlier `\/login` it tells you to run `\/logout` to clear it.\n\n**Details**\n\n- Applies to sessions authenticated through a federated environment setup, where the saved credential can be a Console API key rather than a claude.ai account.\n- A 404 when loading comment threads on an artifact no longer speculates that the artifact was republished.\n- A publish response is now rejected if the returned slug is malformed, not just if fields are missing.\n\n**Evidence**\n\n`a Console API key saved by a previous \/login`\n\n- Area: Artifacts\n- Names: `\/logout`, `\/login`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}