Artifacts for Codex

Codex will happily build you a report, a dashboard, or a one page prototype, and then leave it sitting in your working directory. Getting it to a colleague is your problem: attach it, paste it into a doc, or screenshot it. Point Codex at thing and it can publish the file itself, then tell you the URL it just created.

Connect thing to Codex

Codex keeps MCP servers in ~/.codex/config.toml, or in a project level .codex/config.toml for a trusted repo. Add a table for thing:

[mcp_servers.thing]
command = "npx"
args = ["-y", "@unravel-tech/thing", "mcp"]

[mcp_servers.thing.env]
THING_TOKEN = "paste-your-token-here"

Or let the CLI write it for you:

codex mcp add thing --env THING_TOKEN=paste-your-token-here -- npx -y @unravel-tech/thing mcp

Create the token at usething.ai under Settings, then Tokens. If you have already run thing login in that terminal, the stored credential is used and the token line can go.

What Codex can do once it is connected

Ask it to publish and it calls push_artifact with an HTML page, a Markdown doc, an image, or a PDF, then reports the URL. Push the same name again and you get a new immutable version at the same address, with /diff/1/2 showing what changed between any two. Readers leave comments on the page itself, anchored where the question is. Visibility runs from one named person through team, anyone with the link, and fully public.

The other two tools are list_artifacts, for what you have already published, and whoami, for which account and team it is pushing to.

Not using Codex 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.