Built a place to share the HTML that Cursor generates (paste, fix text by clicking, send a link)

Showcase Built with Cursor
1

A lot of what I make with Cursor ends up as a single HTML file: a report, a small dashboard, a one-off landing page. Then the question is always how to get it in front of someone who doesn’t have the repo.

At work, HTML stopped being a developer thing. Reports, decks, dashboards and invites now come out of AI tools as HTML. Making them got easy. Sharing them is the annoying part:

  • Notion is heavy, and its HTML embed has a lot of limits
  • AI chat share links (like Claude artifacts) are handy, but some expire and they’re hard to find again
  • Asking the AI again just to fix one typo costs tokens and sometimes changes the wrong part
  • .html files don’t open well in a lot of messengers, and people hesitate to open attachments

So I built NOS Workspace for my own team. You paste the HTML code or upload the file and it shows exactly as it was made. Text can be edited right on the page like a normal doc, no touching code. Then you send a link and anyone can open it without an account. Regular docs and HTML pages sit in the same workspace, and there’s version history.

People at work used it more than I expected, so I opened it up. Free plan has unlimited docs and 3 live share links. You can try it on the front page without signing up.

Disclosure: I made it. I’d really like to hear where it breaks or what’s confusing the first time.

5

Correction from the NOS maker: the original post overstated our background. The claims about internal team adoption were not substantiated. The comparisons about other tools expiring or mishandling edits, and the promise that every HTML page looks exactly the same, were also too broad. Please disregard those claims.

NOS Workspace stores existing HTML alongside ordinary documents. A saved share link requires an account for its creator; readers do not need one. The free plan allows three active share links. External images need to be uploaded or embedded, and the rendered result should be checked before sharing. Anyone with a share link can open that page.

Product details: https://nos-workspace.com

6

Nice project. What caught my attention is that some of the behavior is very concrete and testable — the 3 live share-link limit, opening a shared page without an account, editing, and version history.

If you’re still looking for feedback on where it breaks or gets confusing, I’d be happy to try those flows as an outside user and send you what I find. I’ve been exploring ways to independently verify AI-built apps against what the builder intended, and NOS looks like an interesting one to try this on.