Good work.
A real link.
Agents make useful HTML. Let people share it as easily as they share a thought.
Read the proposal ↓“Publish this idea.”
The proposed experience: your agent uploads the file and returns a link. The reader opens it in a browser.
Ready to share.
Still local.
A product idea, an architecture review, a presentation. The agent has already made the document, complete with layout and interactions. But it still lives on one person’s machine.
Turning it into a PDF loses the interactive parts. Deploying a whole site adds work. The opportunity is a small publishing step that keeps the HTML intact.
Start with the handoff.
A complete path from a local file to someone else’s browser.
- Publish one self-contained HTML file through an agent skill.
- Return a sharing link and keep the management key private.
- Update the document while keeping the same URL.
- Offer password protection when the work needs privacy.
Keep the first release small. Revisit these only when the publishing flow proves useful.
- Team libraries and a shared document index.
- Comments, approvals, and review notifications.
- Multi-file websites with asset management.
- Rich editing inside the publishing service.
What would prove it?
Give someone an HTML document they just made. Can they publish it from their agent, send the link, and make a later edit without explaining a new workflow to the reader?
The question to test first
Do people need a place to organize their work, or just a dependable link for the work they already have? This proposal starts with the second need.
This is a sample idea document. Its scope and research questions illustrate a proposal, rather than a product roadmap or measured research.