Claude Artifact Player

That folder-watch + ⌘R reload loop is the dream — I build little audio tool prototypes as Claude artifacts and the browser round-trip kills my flow. Does the offline player handle artifacts that use the Web Audio API / Tone.js for sound, or is it mostly visual right now?

Running interactive TSX/JSX components completely offline is a massive win for privacy. Are these rendered inside an isolated local sandbox like an Electron instance, or how are you handling secure execution locally? Congrats on the launch!

One thing we've noticed with AI workflows is that artifacts often outlive the conversation that created them.Do users mostly revisit artifacts for reference, or are they becoming reusable building blocks that get incorporated into future workflows?

Bundling React 18 and Babel inside a sandboxed WebView to handle JSX/TSX transpilation locally is a smart call. You skip shipping a separate runtime layer while keeping execution fully offline. I've run into the same tradeoff between isolation and dependency freshness. Do you plan to support ESM imports, or do all dependencies need to be bundled at the app level?

Running artifacts locally solves a reproducibility problem that browser-sandboxed execution doesn't. We've built pipelines that generate Claude artifacts as outputs and realized testing them required the browser sandbox, adding friction. How do you handle artifact dependencies locally? Is there a containerized runtime, or does it rely on the host environment's installed packages?

Interesting use case. Does it handle artifacts that make API calls, or doesn't offline mode allow that?

This fixes a very specific Claude workflow problem.Artifacts are great while they’re inside the chat, but once I want to save one, tweak it, reopen it later, or show it like a normal little app, the flow gets awkward.The folder watching and local reload are the details I’d probably use most. It turns artifacts from “cool thing Claude made once” into something I can keep editing on my Mac.

@alsarem I have a question that , how are you handling compatibility as Claude's artifact formats evolve over time , especially for more complex React or TSX based artifacts ?

Claude Artifact Player lets you open and run the interactive files that Claude's Artifacts feature generates — HTML pages, React JSX components, and TypeScript TSX files — directly on your Mac, without a browser and without uploading anything anywhere.WHAT IT DOESClaude (Anthropic's AI) can generate standalone interactive files: data visualisations, UI prototypes, dashboards, calculators, mini-apps, and more. Claude Artifact Player is the fastest way to run those files locally.KEY FEATURES• Open any .html, .jsx, or .tsx artifact file in one click• Watch a folder — the app auto-discovers artifacts as you add files and lists them in a sidebar• Persistent folder memory — your folder is remembered across relaunches• Fully offline — React 18 and Babel are bundled inside the app, no internet required for rendering• Reload with ⌘R while you edit files externally• Reveal any artifact in Finder with a right-clickPRIVACY FIRSTClaude Artifact Player never connects to the internet to render your artifacts. All JSX/TSX transpilation happens inside a sandboxed WebView on your Mac. Your files never leave your machine.WHO IT'S FOR• Developers and designers exploring Claude-generated UI prototypes• Data analysts running Claude-built visualisations and dashboards• Prompt engineers iterating on artifact outputs without copy-pasting into a browser• Anyone who wants to keep a local library of AI-generated interactive toolsREQUIREMENTSmacOS 15 Sequoia or later.Developed by Creative AI Studio — your partner for Generative AI.