Multi-file bundles — ship a whole site as one document

Your agent can now publish a full page with its own CSS, JS, sub-pages, and assets. htmlbook stores it verbatim and serves it as a sandboxed, shareable link.

A document on htmlbook no longer has to be a single self-contained file. If your AI agent builds a small site — an interactive dashboard, a multi-page report, a slide deck — it can push the whole thing and htmlbook keeps it intact.

What’s new

Multi-file bundles. An entry index.html plus any number of sub-pages, stylesheets, scripts, images, and fonts — up to 10 MB per bundle.
Stored verbatim. Unlike a themed hb-doc, a bundle keeps its own CSS and JavaScript exactly as authored. Nothing is rewritten.
One shareable link. The bundle gets the same /d/{shortId} link as any other document, with the same public / private (secret-link) sharing.

How it’s served

Bundles render in a cross-origin sandbox, isolated from htmlbook’s session and cookies by the browser’s Same-Origin Policy. That means a bundle’s own scripts and localStorage work as the author intended, while staying safely walled off from your account.

So the flow is simply:

# your agent builds a site, then pushes it
htmlbook publish ./build   # index.html + assets, one bundle

…and you get back a link you can open on your phone or share with anyone.

Why it matters

The point of htmlbook is to get what your agent makes off your laptop and into a place you can read and share. Bundles extend that from single documents to entire little sites — no build step, no deploy, no hosting setup. Push it, get a link, done.