Agent
Claude Code, Codex, or Cursor writes HTML
Limited-time offerPro & Max plans — 20% offSave 20% on monthly and yearly billing.
Save 20% on monthly and yearly billing.
AI agent mobile preview · Updated September 21, 2026
Claude Code and Codex often run on a laptop or a remote machine while you are holding a phone. localhost is unreachable from that phone. Publish the static HTML with HTMLShare, then tap the preview URL or scan the QR. This is a review step, not a tunnel and not a production host.
The job is to review a finished page away from the computer that wrote it. HTMLShare already supports Codex, Claude, and Cursor, a temporary no-login preview, desktop/tablet/mobile width checks, copy-link, QR code, and Agent Skill.
Claude Code / Codex creates HTML → publish with HTMLShare → get preview URL + QR → open on phone.
Agent
Claude Code, Codex, or Cursor writes HTML
Publish
Skill, CLI, or browser upload
Handoff
HTTPS URL + QR code
Review
Phone browser, no localhost
Claude Code writes reports, dashboards, and prototypes to disk. Those files are local. A phone cannot open a path such as /Users/you/project/index.html or a localhost port on the laptop.
Ask Claude Code for a complete index.html, or a folder with relative CSS, JavaScript, and assets. Build framework projects first.
Install the Skill with npx @htmlshare/cli install --agent all, then say publish this. The agent returns a browser URL.
Tap the URL, or scan the QR on the HTMLShare result screen. Reviewers do not need Claude Code or a Claude login.
If the Artifact tool is missing, this is still the last-mile path: local HTML in, HTTPS preview out. See Claude Code Artifact tool missing and share Claude Code HTML.
Codex can generate a static site or report in one run. HTMLShare Skill can return a preview URL in that same run. Open it on mobile the way you would any other HTTPS page.
For the Codex-specific publish loop, see Codex HTML preview.
One command installs the local Skill for Codex, Claude, and Cursor. After installing, use /htmlshare in any of them to publish the current HTML project.
localhost is the loopback address of one machine. A phone is a different machine. HTMLShare does not expose your running dev server. It hosts a copy of static files so you can review the artifact.
localhost
No
Dev server on that machine
Edit on the computer that is running the page.
LAN IP
Sometimes
Same Wi-Fi, open ports, mixed HTTP
A same-room check when the server stays up.
Tunnel
Yes
ngrok or similar, extra auth
Remote access to a live local server. HTMLShare is not this.
Temporary static preview
Yes
Publish the finished files
Review a report, dashboard, or prototype on a phone.
Production deploy
Yes
Git, project, build, env
After the review, when the page should stay public.
Keep a tunnel if you need live reload against a running server. Keep Vercel, Netlify, or GitHub Pages if you need production. Use HTMLShare when the HTML is already finished and the next job is phone review.
AI prototype QR code
Typing a preview slug on a phone is slow and error-prone. After publish, HTMLShare renders a QR for the same preview URL. Point the camera, open the browser, review the page.
publish → QR code → phone camera → browser preview
HTMLShare also lets you switch desktop, tablet, and mobile widths before you share. That is a first pass. A resized iframe is not the same as Safari or Chrome on the device in your hand.
Agents now run on another computer while you drive them from a phone, Telegram, GitHub, or a similar remote entry. Once the agent writes UI, the next step is opening that UI without sitting at the machine.
phone sends instruction → remote agent edits UI → agent republishes preview → phone opens updated URL → feedback
Sign in through Skill or CLI and publish the first HTML or ZIP. Guest one-hour previews cannot be replaced later.
Store projectId, slug, or the preview URL with the agent run. The phone bookmark and QR should not churn each revision.
Pass CLI --replace. Recipients refresh the original link. This is not a Git history or rollback UI.
Details are on update HTML without changing the URL and MCP HTML publishing.
Review the draft first. Deploy the product later. HTMLShare preview links are noindex, expire by plan, and serve static files only.
See the page on a phone now
URL or QR after publish
Works after project setup
Keep drafts out of Google
noindex responses
You control robots and indexing
Same URL across revisions
Replace on Pro or Max projects
Preview-per-commit or a stable domain
Custom domain, auth, database
Wrong tool
Deploy the app
Guest uploads: 1 MB HTML, 3 MB ZIP, one hour. Signed-in projects: 5 MB for one HTML file, 20 MB for the whole project. Free currently lasts 1 day, Pro 30 days, and Max is described as permanent.
Use one HTML file only when the page is genuinely self-contained. If the agent wrote CSS, JavaScript, images, fonts, or extra pages, keep the folder.
site/ ├── index.html ├── styles.css ├── script.js └── assets/
For the generic AI-output path, see share AI-generated HTML. For a product-review framing, see PRD prototype review.
FAQ
Ask Claude Code to save a self-contained HTML file or a static folder with index.html, then publish it with HTMLShare Skill, CLI, or a browser upload. Open the returned HTTPS URL on your phone, or scan the QR code on the published-result screen. Recipients do not need a Claude account.
Same path as Claude Code. Keep the static files, publish them through HTMLShare Skill or an upload, then tap the preview URL or scan the QR. This is a review link for browser-ready HTML, not a Codex Sites deployment.
localhost belongs to the machine running the page. Another phone cannot open http://localhost:3000 unless it is that same device. For a finished static file, publish a preview URL. For a live dev server you still need to keep running, use a LAN IP or a tunnel. HTMLShare is not a localhost tunnel.
Yes. HTMLShare publishes a temporary noindex preview. Guest uploads last one hour. Signed-in projects follow the current plan’s retention. Use production hosting later if the page needs a custom domain, CI, auth, or a long-lived public site.
Yes, after you install HTMLShare Skill. Run npx @htmlshare/cli install --agent all, then tell Claude Code to publish the HTML. The Skill returns a browser URL you can open on a phone. HTMLShare is not a hosted MCP server today.
Yes. After publish, HTMLShare shows a QR code next to the preview URL on the result screen. Point the phone camera at it to open the live page. The QR encodes the same HTTPS link; it is not a separate hosting mode.
Have the remote agent publish the static HTML and send you the URL. Open it on the phone. Pro and Max users can replace the project for later revisions so the same URL and QR stay current. Free projects and Guest one-hour previews cannot be replaced.
No. Vercel is a fit when you already have a repo, build, env vars, or a production app. A one-off Claude Code or Codex HTML file only needs a review URL. HTMLShare is that preview step, not a Vercel alternative for application hosting.
Yes, when the ZIP is static and includes index.html plus relative CSS, JavaScript, images, and other assets. Guest uploads accept 3 MB ZIP. Signed-in projects accept 20 MB total, with a single HTML file capped at 5 MB. HTMLShare does not run npm install or a server.
HTMLShare preview responses are noindex. That keeps drafts out of search results; it is not password protection, an expiry picker, or a private vault. Anyone with the URL can open the live page.
Publish it, scan the QR, and review on the phone. Keep replace for the next revision of the same page.