Clearer message when an Artifacts request is refused

When 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

You'll noticeTier: how much it should matter to you

1Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

ArtifactsArea: what it touches

ImprovementsKind: in v2.1.311, 26 Oct 26

ImprovementsSection of the release

What

When 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:

one says a permission rule or policy stops it, or that the session's own token (its sign-in credential) no longer works
the other tells you to check /login, /permissions and /config in a terminal

Previously the message always mentioned your claude.ai login and told you to check /login, /permissions and /config.

Why

The guidance now fits where Claude Code is running, including places that are not a terminal, so the advice is easier to act on.

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeImproved screen reader mode: deleting a rule in /permissions says "Deleted allow rule …" right away

See this entry in the whole of v2.1.311 →

The build it came inv2.1.311

26 Oct 2026 · 425 entries, this one is #154.

Use it now29
You'll notice242
Nothing to try yet10
Under the hood144

Either side of it

v2.1.310Older
v2.1.312Newer

Open the release →

Names in this entry

slash/login
Sign in to your Anthropic account
slash/permissions
Manage allow, ask, and deny rules for tool permissions. Opens an interactive dialog where you can view rules by scope, add or remove rules, manage working directories, and review recent auto mode denials. You can also view and edit auto mode classifier rules from the dialog's Auto mode tab. When you run it while Claude is responding, Claude Code opens the dialog immediately and applies your changes starting with Claude's next tool call in the same turn. Before v2.1.234, Claude Code queued the command until the turn finished. Alias: /allowed-tools
slash/config
Open the Settings interface to adjust theme, model, output style, and other preferences. Pass one or more key=value pairs to set a setting directly without opening the interface, for example /config thinking=false, /config theme=dark, or /config model=sonnet. The key=value form also works in non-interactive mode (-p) and from the Claude mobile app via Remote Control. The key=value form can't turn on a setting that needs your confirmation in the panel, such as autoContinueAtUsageLimit, though it can turn one off. Run /config --help to list the keys it accepts. Alias: /settings

Anthropic's note

Upstream's own release notes for v2.1.311 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Improved screen reader mode: deleting a rule in /permissions says "Deleted allow rule …" right away

Is this right?