{"version":"2.1.224","anchor":"new-artifact-login-messages-are-defined-but-not-yet-shown","canonical_anchor":"new-artifact-login-messages-are-defined-but-not-yet-shown","heading":"New artifact login messages are defined but not yet shown","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/new-artifact-login-messages-are-defined-but-not-yet-shown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### New artifact login messages are defined but not yet shown\n\nThree clearer artifact login messages are written but never displayed; you still see the old one.\n\n**What**\n\nThree replacement messages explaining why artifacts need a claude.ai login are defined, covering the plain case, a remote session authenticating through the machine that launched it, and a credential injected by the host environment that takes precedence and cannot be changed. Only the definitions and the module export table appear in this build, with no call site, so the old single message is still what you see.\n\n**Details**\n\n- A fourth builder interpolates the name of the competing credential source into the message.\n\n**Evidence**\n\n`Artifacts need a claude.ai login, but this session authenticates with a credential injected by its host environment, which takes precedence and cannot be changed here. Start a session that is signed in to claude.ai to publish or read artifacts.`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}