Hand someone a page, not a repository.

A friend should not have to install Node to see the thing you made. This is the pass that turns an agent folder into files a browser can open.

1. Find the folder a browser can eat

You are looking for a directory that contains index.html and the assets that page loads. In a lot of agent projects that directory is dist/ or build/. Sometimes the HTML sits at the project root because the agent wrote a single file and stopped. Open index.html locally and click through it. If the only way to see the app is npm run dev, you do not have a page yet. You have a dev server. Ask for a static build, or ask the agent to emit plain HTML, and then repeat this step on the output folder.

2. Make every path work away from your disk

Broken deploys are often path bugs. In the built HTML and CSS, look for:

• http://localhost or 127.0.0.1
• absolute file paths such as /Users/... or C:\
• links that assume a dev-server route you never included in the static folder

Images and scripts should be relative to the page, or absolute on the public host. A path that starts with / is fine only if that file is actually at the root of what you upload. When you are unsure, serve the folder with any static file server and open it from a different machine, or from your phone on cellular. Your laptop lying about missing files is the whole problem you are trying to leave behind.

3. Take the secrets out of the upload

The folder you upload will be readable. Search it for tokens, passwords, and .env values. Build tools sometimes inline them. If you need the page to talk to a data store, the value in the JavaScript should be a public project key, not the token that controls your account. The account token stays in the terminal where you deploy. If you find a secret in the output, rotate it after you remove it. Deleting the file does not un-send a chat paste.

4. Put the folder on an HTTPS address

Upload that folder, not the repository. The visitor does not need your git history, your node_modules, or the agent transcript. They need the static files. Use a host that serves them over HTTPS on a subdomain you can copy. You do not need to pick a clever name tonight, and you do not need to buy a domain to learn whether anyone clicks.

Load the public URL in a private window. Check the pages you actually linked, not only the home page. A single-page app that ships without its fallback route will look perfect on / and empty on refresh of any other path. If that happens, fix the host rewrite or the router before you send the link.

5. Send the page, and say what it is

The message can be one line: the URL, and whether it is public. If the page is a draft for one person, send the access code in the same message and say that the code is the door. If the page is safe to forward, say that too. People hesitate when they cannot tell whether a link is a secret.

Keep the checklist next to the agent. When it offers a cloud account, a container, or a new framework “so we can deploy,” point it back at step 1. The folder with index.html is the whole shipment for this kind of app.