[FEATURE] Ability for Claude Code to reference artifacts created in Claude UI

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude UI allows users to generate files, diagrams, code snippets, and other artifacts, but Claude Code currently has no built-in way to reference or reuse those artifacts directly in the CLI or editor workflow.

This creates friction when switching between Claude UI (where an artifact was created) and Claude Code (where I want to integrate, edit, or extend that artifact). I often need to manually download, copy, or re-paste the artifact into my local workspace, which breaks flow and introduces opportunities for inconsistency or human error.

In practice, artifacts created in Claude UI can be outputs of long prompts, iterative design sessions, or model-generated structures (like complex configs, diagrams, API specs, or code bundles). Without a way to reference these from Claude Code, I lose the ability to cleanly bridge UI work and local development.

Proposed Solution

I would like Claude Code to provide a way to list, reference, and import artifacts generated in Claude UI.

Ideal experience:

• A virtual namespace like /artifacts accessible from Claude Code.
• CLI commands such as:

claude 
/artifacts
/artifacts list  
/artifacts use <artifact-id>  

• Ability to reference UI artifacts directly in Claude Code prompts
• Optional: automatic syncing or selective pull of artifacts into Claude Code workspaces.

This would allow Claude Code to seamlessly use context or files created in Claude UI without manual steps.

Alternative Solutions

Manually downloading artifacts from Claude UI and importing them into Claude Code, but this is error-prone and interrupts flow.

Using cloud storage or GitHub to sync artifacts between UI and CLI—but this requires extra setup and still doesn’t allow Claude Code to reference artifacts directly by ID.

Re-asking Claude to regenerate the artifact, which is unreliable and can diverge from the original output.

Other tools solve this through shared cloud storage or unified artifact repositories, but Claude UI and Claude Code currently feel siloed in this regard.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

1. I ask Claude UI to generate a PRD.
2. The artifact is created inside Claude UI.
3. I then open Claude Code to implement or modify the system based on that artifact.
4. Today, I have to manually download or copy the artifact or use Claude Code to generate the plan.
5. With this feature, I could run:

claude 
/artifacts

1. Claude Code would show options to pull, list and use artifacts that were generated in Claude UI.
2. This preserves continuity, prevents inconsistencies, and saves a lot of time.

Additional Context

• A unified artifact API would also benefit teams using Claude UI for prototyping but Claude Code for building real systems.
• A /artifacts mount could behave similarly to a read-only remote filesystem.