Set up Thing in Pi coding agent
Pi can publish using its shell tool. You do not need to add an MCP extension to get your first artifact online.
Already connected? Publish your first artifact
Connect thing to Pi
Install Node.js LTS so npx is available where Pi runs. In that terminal, authenticate once:
npx -y @unravel-tech/thing@latest login
Open Pi in your working directory and paste the publishing prompt below. Allow the shell command after reviewing the file.
Optional: keep the publishing skill for future sessions
Install Thing’s Pi-compatible skill package:
pi install git:github.com/unravel-team/thing
Reload or restart Pi to discover the skill. The package teaches publishing; the CLI itself is fetched from @unravel-tech/thing.
Pi skills documentation. If Pi runs in a container or remote workspace, authenticate there; it does not inherit credentials from your laptop.
Publish your first artifact
Paste this into Pi. It creates a real artifact; no existing file is required.
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 default private, and team artifacts default team-visible. Invite a person or choose the visibility you need.
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.
Not using Pi 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.