[BUG] Artifact tool not loaded in claude -p even with enableArtifact: true in user settings

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The Artifact tool is never loaded in print mode (claude -p), even with "enableArtifact": true in user settings (~/.claude/settings.json). This makes it impossible to republish an existing artifact from a script or cron job.

The docs (https://code.claude.com/docs/en/artifacts#availability) say Artifact is "Off by default in Agent SDK, GitHub Action, and MCP-server contexts", but the enableArtifact setting description (https://code.claude.com/docs/en/settings) says it enables the tool "for this user" and only lists managed disableArtifact and org admin settings as overrides — it does not mention being ignored in SDK/print context. Either enableArtifact should take effect in -p, or its documentation should state the limitation and there should be some supported way to enable Artifact for headless runs.

Artifact works fine in interactive sessions on the same machine and account.

What Should Happen?

Either enableArtifact: true (user scope) loads the Artifact tool in -p, or a documented flag exists to enable it in SDK contexts.
With "enableArtifact": true in ~/.claude/settings.json, the Artifact tool should be available in claude -p, so a prompt like claude -p "Update https://claude.ai/code/artifact/<id> with fresh data" republishes the existing artifact to the same URL — same behavior as an interactive session.

Alternatively, if enabling Artifact in SDK contexts is intentionally unsupported, the enableArtifact docs should say so explicitly and an enablement mechanism (flag or setting) should be provided for headless automation.

Error Messages/Logs

Prompting an artifact update in -p returns the literal error:
"Artifact exists but is not enabled in this context"

The `tools` array from the init event (`--output-format stream-json --verbose`) does not include "Artifact":
["Task","Bash","CronCreate","CronDelete","CronList","DesignSync","Edit","EnterWorktree","ExitWorktree","ListMcpResourcesTool","Monitor","NotebookEdit","PushNotification","Read","ReadMcpResourceDirTool","ReadMcpResourceTool","RemoteTrigger","ReportFindings","ScheduleWakeup","SendMessage","Skill","TaskCreate","TaskGet","TaskList","TaskOutput","TaskStop","TaskUpdate","ToolSearch","WebFetch","WebSearch","Workflow","Write", ...mcp tools...]

Steps to Reproduce

1. Linux server, Claude Code v2.1.215, logged in with a claude.ai Max account via /login (OAuth; apiKeySource: none). No managed settings, no CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, no disableArtifact anywhere.
2. Create an artifact from an interactive session (works fine) and note its URL.
3. Add "enableArtifact": true to ~/.claude/settings.json.
4. Verify that user settings ARE loaded in -p: add "model": "claude-haiku-4-5" to the same file and run claude -p 'x' --output-format stream-json --verbose — the init event reports the haiku model, proving the file is read. Remove the key again.
5. Run: claude -p 'hola' --output-format stream-json --verbose and inspect the tools array in the init event → "Artifact" is absent.
6. Run: claude -p 'Update https://claude.ai/code/artifact/<id> with a test line' --allowedTools "Artifact" → model replies it has no artifact tool; in earlier runs it returned "Artifact exists but is not enabled in this context".
7. Also tried --settings ~/.claude/settings.json explicitly → same result.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.215

Platform

Other

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

Use case: a cron job that republishes an existing artifact (fixed URL shared with the team) with fresh data daily. Currently the only workaround is driving an interactive session via tmux send-keys, which is fragile for automation.

~/.claude/settings.json at time of testing:
{
"permissions": {
"allow": ["mcp__ops-mcp", "mcp__ads-mcp-staging"],
"ask": ["mcp__ops-mcp__deploy_production", "mcp__ops-mcp__detener_servicio"]
},
"theme": "dark",
"remoteControlAtStartup": true,
"agentPushNotifEnabled": true,
"skipWorkflowUsageWarning": true,
"enableArtifact": true
}

dev@YYYYYYYY:~$ claude -p 'Update https://claude.ai/code/artifact/ID with a test line' --allowedTools "Artifact" --permission-mode acceptEdits
I can't do it — the `Artifact` tool isn't available in this session.
dev@YYYYYYYY:~$ claude --version
2.1.220 (Claude Code)