◈OpenTree DashboardSign in

$ # no localhost required

You do not need a tunnel to show someone one HTML file

Reaching for a tunnel to show a colleague a page is a habit from when the page was served by something running locally. When the artifact is a static file — which agent output almost always is — the tunnel is doing nothing except keeping your laptop in the loop.

When a tunnel is the right tool

When there is a live process on the other end. Testing a webhook against a local server, demonstrating an application mid-development, letting a mobile device hit your dev environment, debugging something with real inbound traffic. In all of those the value is exactly that the request reaches your machine.

When it is the wrong tool

When the artifact is finished. Then the tunnel adds three failure modes for no benefit: the link dies when your laptop sleeps, the URL changes when the tunnel restarts, and whoever you sent it to gets an error at the exact moment they get around to looking. It is also, briefly, a public route into your machine.

The alternative

curl -X POST https://read.botook.ai/sites \
  -H "Authorization: Bearer otr_live_YOUR_KEY" \
  -F file=@index.html

The file is now on a URL that does not depend on your machine being awake, does not change, is not indexed, and closes itself when its expiry arrives.

Side by side, for the static case

TunnelPublish
ServesA process on your machineA stored document
Survives sleepNoYes
Stable URLNot on the free tierYes
Access controlBasic auth if configuredPassword, email gate, one-time, expiry
ExposureA route into your machineOne document
CleanupKill the processExpires on its own

Keeping the iteration loop

The reason people like tunnels is that the page updates when they save. You keep that with one extra call — update_site or PUT /sites/:idOrSlug rewrites the bytes under the same URL, so a watcher script or an agent loop gives the same experience without exposing the machine.

What if my page calls a local API?

Then you have a process, not a file, and a tunnel is the right tool. Publish the static view of it — the report, the screenshot-shaped summary — and keep the tunnel for the live parts.

Yes, with set_password or a PATCH. You can also gate on a work-email domain, which forwarding does not defeat.

How fast is this compared to starting a tunnel?

One HTTP request against about the same. The difference is what happens twenty minutes later when you close the laptop.

Can an agent do it mid-session?

That is the primary path — publish_html over MCP, no shell-out and no tunnel process to supervise.

Keep reading