Set up thing in Claude Code

Keep building in your repository. Let Claude Code publish the report, prototype, or document when it is ready for someone else to see.

Already connected? Publish your first artifact

Connect thing to Claude Code

Install Node.js LTS if npx --version does not work. From Claude Code’s terminal, publish a file with the public npm package:

npx -y @unravel-tech/thing@latest push report.html

The first push opens browser approval when needed, then resumes automatically. No GitHub repository or plugin access is required.

Review the file before publishing. The CLI is published as @unravel-tech/thing on npm; its source is in the public thing-cli repository.

Publish your first artifact

Paste this into Claude Code. It creates a real artifact; no existing file is required.

Your first-publish prompt

Create a small self-contained HTML report named first-thing.html about this project. Let me review it, then run npx -y @unravel-tech/thing@latest push first-thing.html --name first-thing --visibility private --json and return the URL.

The agent should return a thing URL. Open it while signed in and confirm the report is there. Check Share before sending it. Personal artifacts open for anyone with the link; to keep a report restricted, push it to a team, where artifacts default to team-only and you can invite people one by one.

For your next report, use the same name to add a version at the same URL.

Something not working?

Check npx --version, then run npx -y @unravel-tech/thing@latest whoami on the machine running your agent. If sign-in is missing, run npx -y @unravel-tech/thing@latest login there and restart the agent. For MCP, confirm thing’s tools appear before asking it to publish. Never put credentials in a prompt or a committed config.

Try the direct terminal command or upgrade an older CLI.

Not using Claude Code for everything?

The same artifacts work from every other agent, and from CI. See artifacts for any coding agent for Claude Code, Aider, Cline, shell tools, and pipelines, and for why a page that outlives the session it came from is worth the extra step of publishing.

Check your published artifacts Choose another setup