{"version":"2.1.224","anchor":"artifact-tool-now-explains-exactly-which-credential-is-block","canonical_anchor":"artifact-tool-now-explains-exactly-which-credential-is-block","heading":"Artifact tool now explains exactly which credential is blocking it","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/artifact-tool-now-explains-exactly-which-credential-is-block","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Artifact tool now explains exactly which credential is blocking it\n\nThe artifact tool now names the exact credential blocking you, with a fix for each.\n\n**What**\n\nWhen you are not logged in, both the input check and the tool call stop immediately and name the credential source that is standing in the way: the `ANTHROPIC_API_KEY` environment variable, the `apiKeyHelper` setting, a token file descriptor, or a Unix socket, each with its own fix.\n\n**Details**\n\n- for the environment variable the advice is to unset it, or run `\/logout` and decline the API key approval before logging back in\n\n**Evidence**\n\n`Unset the ANTHROPIC_API_KEY environment variable, or claude \/logout then say \"No\" to the API key approval before login.`\n\n- Area: Artifacts\n- Names: `ANTHROPIC_API_KEY`, `apiKeyHelper`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}