display.dev for OpenAI Codex
Codex runs the code. display.dev is where the output lands – at a permanent URL, behind your company login when you want it. One command. Your team can see it in 15 seconds. And because display.dev works with any agent, the URL outlives your tool choice – rotate to a different agent next quarter and everything you published stays exactly where it is.
Codex produces output. Sharing it is broken.
OpenAI Codex – whether you're using the Codex CLI, the API, or the sandbox – generates real output: data analysis reports, web tool prototypes, interactive HTML visualizations, scraper results rendered as dashboards.
That output is local. There's no built-in path from a Codex-generated HTML file to a company-restricted URL.
The workarounds are the same as always: screenshot (loses interactivity), Slack upload (downloads as a file), GitHub Pages (excludes non-engineers), Vercel (requires a git project, $320/month for SSO).
None of them fit the Codex workflow. display.dev does.
From Codex output to company URL
Direct publish:
dsp publish ./analysis.html --name "weekly-analysis"In a Codex pipeline:
codex run analysis.py --output ./report.html
dsp publish ./report.html --name "analysis-$(date +%Y%m%d)"Via agent tool call (MCP):
{
"name": "publish",
"arguments": {
"content": "<html>...",
"name": "codex-output-2026-w15"
}
}The URL is permanent. Paste it in Slack or email. Your team clicks it, authenticates with their company email once, and sees the full interactive result.
What Codex generates – and what display.dev publishes
| Codex output | Use case |
|---|---|
| HTML data analysis report | Share with stakeholders without a BI tool |
| Interactive visualization | D3, Chart.js, Plotly output from a data run |
| Web tool prototype | Internal tool built with Codex agent |
| Scraper output dashboard | Competitive monitoring, market data |
| Multi-file static app | dsp publish ./output/ |
Any HTML that Codex writes to disk. display.dev serves it as a rendered page, not a download.
For Codex as an agent
When Codex runs autonomously – generating reports, building tools, producing analysis – it can publish its own output via display.dev's MCP tool.
The agent invokes the publish tool with the HTML content and a name. display.dev returns a company-gated URL. The agent includes the URL in its final response or posts it to Slack.
No human in the loop for publishing. The output arrives at a permanent, authenticated URL automatically.
This is the agentic publishing primitive: agent produces content → content is immediately accessible to the right people → no sharing step required from the engineer.
Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 90 days audit logs
For compliance-driven organizations.
From $499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 365 days audit logs
Features
Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.
Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. The artifact stays a living document, not a one-shot screenshot.
dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Claude Code, Codex, and Cursor all work, along with anything else that creates HTML or Markdown output.
Common questions.
Does this work with the Codex CLI and the Codex API?
Yes. display.dev's CLI publishes any HTML file on disk – it doesn't care which tool generated it. For programmatic publishing from the Codex API, use display.dev's REST API or MCP tool.
Can Codex publish its own output automatically?
Yes. Configure display.dev as an MCP tool in your Codex agent setup. The agent invokes the publish tool and receives a URL to include in its response or post elsewhere. No manual step required.
Do viewers need an OpenAI account?
No. Viewers authenticate with their company Google or Microsoft email. No OpenAI subscription required.
What if the Codex output is a multi-file directory?
Run dsp publish ./output/ to publish the entire directory. display.dev serves index.html at the root and resolves all relative asset references.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).