{"version":"2.1.311","anchor":"artifacts-withheld-bearer-refusal-message-changed","canonical_anchor":"artifacts-withheld-bearer-refusal-message-changed","heading":"Clearer message when an Artifacts request is refused","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/artifacts-withheld-bearer-refusal-message-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Clearer message when an Artifacts request is refused\n\nWhen Artifacts is blocked, the error now says a rule, policy or expired token is the cause, or points to \/login, \/permissions and \/config in a terminal\n\n**What**\n\nWhen Claude Code will not send an Artifacts request because the session can no longer use Artifacts, the message now comes in two versions depending on the situation:\n\n- one says a permission rule or policy stops it, or that the session's own token (its sign-in credential) no longer works\n\n- the other tells you to check `\/login`, `\/permissions` and `\/config` in a terminal\n\nPreviously the message always mentioned your claude.ai login and told you to check `\/login`, `\/permissions` and `\/config`.\n\n**Why**\n\nThe guidance now fits where Claude Code is running, including places that are not a terminal, so the advice is easier to act on.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}