Artifacts for any coding agent

Your agent built something worth showing a person: a report, a dashboard, a prototype, a doc. thing turns that file into a live page at a durable URL, with versions, diffs, comments on the page, and sharing that ranges from one named person to fully public. It does not care which agent produced the file.

Coming from Claude Artifacts?

The artifact is the right unit: one page you can hand someone, rather than a transcript or a file they have to open. The limit is that a page created inside a chat belongs to that chat. thing keeps the unit and drops the binding. The link is yours, not a session's. Access is a range rather than a switch, so a single client can read it without the whole internet reading it. Pushing the same name again adds a version at the same URL, and /diff/1/2 shows what changed. Questions land as comments on the page itself. And the thing that produced it can be any agent, a CI job, a cron script, or you at a terminal.

One command, whichever agent you use

$ npm i -g @unravel-tech/thing
$ thing login
$ thing push report.html
  https://usething.ai/you/report · v1 · html
$ 

• Claude Code: install the plugin with /plugin marketplace add unravel-team/thing, then /plugin install thing@thing. The bundled skill checks login and pushes for you.
• Codex, Cursor, and any MCP client: point it at the MCP server. Command npx, args -y @unravel-tech/thing mcp, and THING_TOKEN in the environment.
• Gemini CLI, Aider, Cline, or a shell tool: the agent runs thing push like any other command. Add --json when it needs to read the URL back.
• CI pipelines and cron: set THING_TOKEN as a secret and push the build output. No interactive login.

Setup pages with the exact config: Codex, Cursor, Gemini CLI.

What the link gives you that a file does not

• Every push is immutable. The plain URL serves the latest version, /v/N is permanent, and a diff shows what moved between any two.
• Readers comment on the page, anchored where the question is, instead of replying in a separate thread.
• Visibility runs private, team, anyone with the link, or public, plus per person viewer, editor, and owner grants.
• HTML renders as itself, Markdown renders in a reader view, and images and PDFs open inline.