[Bug] Artifact tool missing from all surfaces for single Team account since 2026-07-28
Bug Description
Title: [BUG] Artifact tool absent from all surfaces for a single Team-plan account (CLI + claude.ai web + New artifact) since ~2026-07-28; org unaffected
## Summary
The Artifact tool is not registered in any session for my account, across every
surface: Claude Code CLI, claude.ai web chat, and the claude.ai/artifacts
"New artifact" entry point. Claude falls back to writing a local HTML file. On
web it presents the HTML file as an artifact ("an artifact just is a file
written to the outputs directory"), which appears to be confabulation when the
tool is unavailable — nothing is created and nothing appears in my gallery.
Artifacts worked on this account for weeks and stopped ~28 July 2026. My
organization is unaffected: coworkers on the same Team org published artifacts
on 7 and 10 August 2026.
## Onset — pinned independently by two signals
- skillUsage["artifact-design"] in ~/.claude.json: usageCount: 13,
lastUsedAt: 1785265172528 (2026-07-28). Nothing since.
- claude.ai/artifacts gallery: prior artifacts still listed and viewable, all
"Edited 2 weeks ago" as of 2026-08-11.
## Requirements verified
| Requirement | Status |
| --- | --- |
| Plan | Team — artifacts on by default; Enterprise RBAC role scoping N/A |
| Org capability | Artifacts toggle on; coworkers published 2026-08-07 and 2026-08-10 |
| CLI version | 2.1.226 (min 2.1.183) |
| Auth | /login claude.ai Team session; ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN unset |
| Model provider | Anthropic API (reproduces on Opus 4.8 and Opus 5) |
| Local settings | No disableArtifact; no Artifact in permissions.deny (user + local); CLAUDE_CODE_DISABLE_ARTIFACT and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC unset |
| Managed policy | /Library/Application Support/ClaudeCode/managed-settings.json does not exist |
| Org policy | ZDR/CMEK/HIPAA not available on Team |
## Also ruled out
- Adding "Artifact" to permissions.allow — no effect
- Child vs top-level session (CLAUDE_CODE_CHILD_SESSION set vs unset) — reproduces in both
- /login re-auth — cached feature-flag values unchanged afterward
- claude --debug — logs no gating decision for artifacts
## Possibly relevant
Cached GrowthBook values in ~/.claude.json: tengu_plan_artifact,
tengu_md_artifact_styling, and tengu_retire_chat_relay_artifact_backstop are
all false; tengu_frame_publish_context is true. Noting these for
completeness — false is the default for most flags there, and no
tengu_*artifact*_tool flag exists, so these may be incidental.
Reproduces the diagnostic from #80418: built-in agent-type definitions still list
Artifact in their tool-exclusion lists ("All tools except Agent, Artifact,
ExitPlanMode, ...") while the tool is absent from the session registry — the
client ships the concept but never receives the grant.
## Relation to #80418
Same symptom, different scope. #80418 is org-wide, CLI-only (claude.ai web
unaffected), onset ~16 July. Mine is single-account, all-surface (web included),
onset ~28 July, in an otherwise healthy org. Filing separately since the
org-scope diagnosis there does not fit.
## Expected vs actual
- Expected: Artifact tool available; artifacts publish to claude.ai.
- Actual: tool absent from every surface for this account; local HTML file
written instead.
Environment Info
- Platform: darwin
- Terminal: vscode
- Version: 2.1.226
- Feedback ID: 5604ea08-b2e0-4be4-a0fc-aea4a3af702a
Errors
[]