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.

Already connected? Publish your first artifact

Connect thing to Codex

With Node.js LTS installed, sign in and register Thing from the terminal on the machine running Codex:

npx -y @unravel-tech/thing@latest login
codex mcp add thing -- npx -y @unravel-tech/thing@latest mcp
codex mcp list

Restart your Codex session and ask it to call Thing’s whoami tool. Alternatively, merge this into ~/.codex/config.toml:

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

This uses your saved Thing login, without a token in the config. A remote Codex environment needs its own authentication. See the official Codex MCP documentation for configuration and tool controls.

Publish your first artifact

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

Your first-publish prompt

Use Thing’s whoami tool to confirm my account and team. Create a small self-contained HTML report, let me review it, then call push_artifact with inline content, filename first-thing.html, and name first-thing. Omit visibility to use the workspace default. Return the URL and its visibility.

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.

Try the direct terminal command or upgrade an older CLI.

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.

Check your published artifacts Choose another setup