Tunly1. Ask for a finished HTML file
If your AI response is a block of HTML, copy only the code into a plain-text file named index.html. Ask for CSS and JavaScript to be included in the file, without external libraries. A useful instruction is: ‘Return one complete, responsive HTML file with inline CSS and JavaScript. Use the content I provided. Do not add network requests, external assets or a backend.’
2. Preview the page before sharing
Open the HTML viewer, choose the file or paste its contents, and select Preview HTML. Check both desktop and phone widths. Scripts are off initially. Enable interactions only when you trust the code. The local viewer blocks network requests and browser storage, so external fonts, remote images and API calls will not work there. Nothing is uploaded to Tunly by the viewer.
3. Give your page a Tunly link
Publishing is a separate step from the local viewer. Install the Tunly CLI using the developer guide, sign in, and publish the saved HTML file. Your coding agent can run the same commands. The following example shares with signed-in members of your namespace; use --public instead only when anyone with the link should be able to read the content.
tunly login
tunly publish index.html --account4. Add feedback when you need it
For a report or proposal that needs discussion, publish with Review enabled. Open the returned review_url to select text and start a comment thread. The raw page URL and the review URL serve different reading experiences.
tunly publish index.html --review --account5. Check what your recipient sees
Test the returned link with the account and sharing settings your recipient will use. A local file address beginning with file:// cannot be opened on someone else’s device. A public URL can be forwarded; non-public access requires an active Tunly login and permission. User-published content asks search engines not to index it, but that is not an access restriction.
If your AI made a whole application
This workflow fits finished HTML and built static sites. JSX, TSX and source folders that depend on a build step must be built first. Apps requiring a database, server-side code or external authentication also need their own running services. For an existing local app or a static output folder, see the developer documentation rather than uploading source code as HTML.