Add a "Local files" section beside Artifacts for HTML generated on disk

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 21, 2026

What I'm trying to do

Claude Code often writes HTML deliverables to my local filesystem — reports, explainers, small dashboards. The Artifacts pane lists only pages published to claude.ai, so there is no equivalent surface for the local ones. Pages I asked Claude to write end up scattered across the working directory and per-session scratchpad folders with no way to find or open them from the app.

What I'd like

A section in the side pane, next to Artifacts, listing the HTML files Claude has generated locally for this project, with click-to-open showing the rendered page.

Why the existing surfaces don't cover it

1. The Files pane opens one file at a time and shows source, not the rendered page.

2. The Browser pane loads a local file as a data: URL snapshot. Opening file:///.../index.html returns "files outside the project folder render as static snapshots" and the tab origin becomes data:. Relative links then have no base to resolve against, so clicking any link in a local index page silently loads a blank page with no error. To a user this looks like something is being blocked; in fact the navigation has no target.

Worth noting: I saw that message and behaviour for a file that was inside my working directory (<workdir>/html/index.html with the session rooted at <workdir>), so either the wording is wrong or the containment check is stricter than it reads.

3. Publishing the index as an artifact doesn't help — a claude.ai-hosted page cannot open file:// links, so the list renders but nothing in it is clickable.

Workaround

I ended up writing a small static file server and pointing the Browser pane at http://localhost:<port>. Links work fine over HTTP. That is a lot of scaffolding for "show me the page you just wrote."

Environment

  • Claude Code, desktop app (Code tab)
  • Windows 11

View original on GitHub ↗