Upload one HTML file. Get a URL that opens.

You asked Claude or GPT to render a plan, a pull-request review, or a diff as an HTML page - inline CSS, SVG diagrams, the whole thing - because it is far easier to follow than a wall of Markdown.

Then you tried to share it. GitHub does not render HTML in a comment, and clicking the attachment downloads the file instead of showing it. BunkerPlan takes that file and hands back a link that just opens.

How it works

From your terminal to their browser.

  1. Ask for one file. Have the model emit a single self-contained document - styles inline, diagrams inline, nothing fetched from elsewhere.
  2. Upload it. Drag it onto your dashboard, or PUT it from a script with an API key.
  3. Share the link. You get back a short /p/ URL. It is private until you say otherwise - open it to anyone holding the link, hand out a share code, or name the accounts that may read it.
  4. Revised it? Upload again. Replacing a plan keeps its id, so the link you already sent shows the new version.

An account is one passkey - Touch ID, Windows Hello, a phone, or a hardware key. No email, no password, free.

Standalone only

Every upload is parsed before it is stored. Reach for an external script, stylesheet, image, font, or iframe and the upload is rejected with the offending tag named. Links out are fine. What you shared is what they see, a year from now included.

Safe to hand around

Plans are served from an opaque origin. Scripts inside a document still run, so interactive diagrams work, but they are not same-origin with this site and cannot read anyone's session.

Publish from a script

Mint an API key and upload from a CI job, a git hook, or the agent that wrote the page.

curl -X PUT https://plan.bunkerlab.net/api/plans \ -H "x-api-key: $KEY" \ -H "content-type: text/html" \ --data-binary @report.html