Your agents now write more than anyone can read.

Most of it never reaches the people it was for.

Let agents generate code.
thing generates understanding.

Your agent publishes what it made to one durable link: reports, dashboards, memos, diagrams. Your team reads the same page, leaves notes on the exact passage, and sees what changed in each version.

Paste this into Claude Code, Codex, Cursor, or any agent

Set up thing: https://usething.ai/llms.txt

Reads the setup notes at /llms.txt.
Writes a small welcome page and asks before publishing it.
Has you approve sign-in in your browser, then hands you the link.

Step-by-step setup Read a live artifact

So the wall of text gets pasted into Slack. thing turns it into pages people read.

Four thousand words dropped in a channel. Someone asks for the tl;dr, someone asks which version is current, and by Friday it has scrolled away.

Share a link instead of a paste. Reports, decks, dashboards, notebooks, each with its versions and notes on the exact passage.

Understanding is not a summary. It is people looking at the same page and saying what they see.

How a team gets to understanding

Four things a paste can never do.

One link that stays true.

A paste is a snapshot nobody can find again. A thing link is the page itself: the plain URL always shows the latest version, and every earlier one keeps its own address.

When the agent revises, /diff/1/2 shows what moved, so the conversation picks up where it left off. If a version was wrong, roll back in one click.

v1v2v3+2 −1

- p95 held near 420 ms until the deploy.+ p95 held near 420 ms until the 9 Oct+ deploy, then rose to 780 ms.  Re-enabling the cache is the fix.

/acme/q3-report/v/2Restore v2

Notes land on the sentence they are about.

Select a passage or mark a region of a chart and say what you see. Replies stay in the thread, threads get resolved, and every note remembers the version it was written on.

Disagreement shows up early, while it is still cheap, instead of in a meeting three weeks later.

Activation, not acquisition, is the constraint this quarter. We propose moving two engineers to onboarding.

Priya S.2h

Where are the activation numbers behind this?

Lee K.1h

Appendix B. Pulling them onto page 2 in v2.

ReplyResolve

Pages that ask questions back. Beta

With Inputs, the page your agent builds can ask the people reading it what they think, right next to what they just explored. Each answer is tied to the version they saw, and people can change it later.

You read every response privately, with its history and a CSV, and find out where people actually differ. Your agent can write the report view to suit the question.

If the rollout fails at 10%, would you continue?

Pause and roll back

Continue to 25%

Continue to everyone

Why? Rollback takes an afternoon, not a click.

Submit responseSigned in as Lee K.

Responses12Export CSV

Person	Choice	Version
Lee K.	Pause and roll back	v3
Ana R.	Continue to 25%	v3
Sam O.	Pause and roll back	v2
Priya S.	Continue to 25%	v3

Your agent did the work. Now let people read it.

Publish from the agent you already use

One command, any agent, one durable link back.

Start with the Claude Code plugin.

Two commands, then "share this report" is all you type. The skill pushes the page your agent made, signs you in through the browser on the first push, and hands back the link.

HTML with its assets, Markdown, PDFs, and images. --json output for agents, and thing mcp for agents without a shell.

$ thing push q3-report.html --json
Opening sign-in in your browser. Approved.

usething.ai/acme/q3-report

v1 · html · team

Copy link

htmlmdpdfpngjpgwebp

Built for teams

Owner, admin, and member roles
Search, filters, and labels
SSO with Okta, Azure AD, or Google
Turn off public links org-wide
Audit log with CSV export
Your logo on every artifact page

Prefer manual setup?

Your first push is one command

Run it on an HTML page, Markdown document, image, or PDF. On the first push, thing opens sign-in in your browser, waits for approval, then resumes and prints the durable URL.

$ npx -y @unravel-tech/thing@latest push report.html
  Opening https://usething.ai/device?user_code=7GKD-42QX
  Waiting for approval…
  Logged in as you@company.com
  https://usething.ai/you/report · v1 · html

Push the same file again to add v2. Add --team, --visibility, or --json as needed.

Or let the Claude Code plugin push for you

The bundled skill runs thing push and handles first-time approval. Replacing an older global install? Follow the CLI setup and upgrade guide.

/plugin marketplace add unravel-team/thing
/plugin install thing@thing

Let agents generate code.thing generates understanding.