NOS: paste an HTML page, fix its wording on screen, and share it as a link

[nosworkspace]

I'm building NOS, where you can paste an HTML page you already have, fix its wording right on the rendered page, and send it to someone as a link.

Once you paste the page in, NOS shows it as a rendered preview. If a line is wrong, you click that text and type the correction, and the edit goes back into the original HTML. When it reads right, you share it as a NOS-hosted link without deploying a site of your own, and the person who opens it doesn't need to log in. Pasting and previewing work without an account. You only sign in when you create the link, and the free plan includes three share links.

Here's a made-up example. Say you have a one-page project update as an HTML file and want a teammate to read it before a review. You paste it in, change ‘beta in October’ to ‘beta in November’, correct a misspelled name, and send the link. If the date moves again, you fix it on the page and the link you already sent stays the same. The page also stays in your workspace next to your notes instead of in a downloads folder.

We've used Codex while working on NOS. One example is the preview entry on one of our guide pages: you open the card there, paste your own HTML, and see it rendered without signing up.

https://nos-workspace.com

Claude helped draft this post.

[TheodorNEngoy]

I tried the no-signup preview with a small fictional project update. Changing “October” to “November” on the page also updated the HTML field, and the new wording remained in the phone preview.

The next example I'd find useful is the return to Codex: after I correct wording in NOS, I ask Codex to change the layout. Is copying the edited HTML back into Codex the intended route today? A short example showing how those manual edits survive the next revision would help. I saw that the direct MCP save connection is still planned.

Written with Codex assistance.

[nosworkspace]

The manual route starts with the HTML after your text edits. That field updates when you correct a line on the page.

With your example: change October to November in NOS, copy the updated HTML, and ask Codex to change the layout while keeping that wording. Bring the result back into NOS and check November is still there before saving. The next revision then starts from your corrected source, though I would still check the result rather than assume the AI preserved every word.

This is the copy-and-paste route; it doesn’t use a direct save integration.