Inplain.
Ausprobieren

Agent-generated HTML delivery

Share agent-generated HTML as a browser link

Turn a self-contained HTML report, dashboard, prototype, or lesson from Claude Code, Codex, Cursor, or another agent into a URL that a non-technical recipient can open.

The short answer

Ask the agent for one self-contained HTML file, inspect it locally, remove secrets, then drop it into Inplain. You get an HTTPS link without creating a repository, configuring a server, or asking the recipient to download the file.

Start with a reviewable local file

  • One self-contained .html file with its CSS and JavaScript included
  • A report, dashboard, prototype, diagram, lesson, or interactive demo
  • Content already checked for secrets, private data, and factual errors

Deliver something another person can open

  • An HTTPS link that opens in a normal browser
  • No installation or Inplain account required for the viewer
  • A seven-day anonymous link, with an option to sign in and keep it

A safe three-step handoff

  1. 01

    Generate one file

    Ask Claude Code, Codex, Cursor, or another agent for a self-contained HTML file. Local file paths, server routes, and private package imports will not work for a recipient.

  2. 02

    Inspect before publishing

    Open the file locally, verify the content and interactions, and remove API keys, personal data, internal URLs, analytics, and any asset the page should not load remotely.

  3. 03

    Publish and send the URL

    Drop the file into Inplain, copy the returned HTTPS link, and test it in a private browser window before sending it to a client, teammate, or student.

A reusable brief

Reusable agent prompt

“Create one self-contained HTML project update. Include the decision, evidence table, risks, and next actions. Put all CSS and JavaScript in the file, use no local assets or secrets, and save it as project-update.html so I can publish it as a browser link.”

The agent still owns generation; Inplain handles the last mile from a local file to a link. The recipient sees the rendered page instead of source code, a ZIP archive, or a setup guide.

Why the last mile needs its own workflow

Public issue reports show recurring failure modes around artifact permissions, authenticated frames, and HTML that cannot be shared publicly. A separate delivery step is useful when the requirement is simply: inspect one local file, publish it deliberately, and give the recipient a normal URL.

What this workflow does not do

It does not deploy a backend, resolve local asset paths, secure secrets embedded in the file, or make untrusted HTML safe. Anonymous links expire after seven days. Review the source before publishing and use a full hosting or access-control platform when the page needs server code, private authentication, or production operations.

FAQ

How do I share HTML generated by Claude Code without setting up hosting?
Save the result as one self-contained .html file, open it locally to verify it, then drop it into Inplain's HTML-to-URL tool. It returns an HTTPS link without a repository, build command, or hosting account.
Does this also work with Codex, Cursor, Gemini CLI, or another agent?
Yes. The publishing step is agent-agnostic: it accepts a local HTML file. The file must contain or remotely reference everything it needs; local paths and server-only code will not work for the viewer.
Does the person opening the link need an Inplain account?
No. A viewer can open the published link in a browser without signing in. The publisher only needs an account to keep and manage an anonymous link beyond its seven-day lifetime.
Can I publish an HTML file that contains API keys or private customer data?
Do not publish secrets or sensitive data inside client-side HTML. Anyone who can load the page can inspect its source and network requests. Remove secrets and use an access-controlled application when the content is private.
Can the link run a Node, Python, or database backend?
No. This workflow publishes a browser-rendered HTML artifact, not a server application. Choose a full deployment platform when the output requires server code, environment variables, a database, or private authentication.