Launched this week

Glass Page
A place for people to review an agent's work
85 followers
A place for people to review an agent's work
85 followers
I built Glass Page after my agent wrote a system design doc that I wanted my team to comment on. Now Claude, ChatGPT, Cursor, Codex or any agent on MCP can publish what it makes as a Pane with a link. A Canvas lays the Pages out on that link so you can pan and zoom. Your team leaves Comments in Threads, on the exact spot. The agent reads them and replies with a new Version, and one Latest Link always shows the current one. Free for up to 10 Panes.






Free Options
Launch Team / Built With

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted

Hey everyone, I'm Nabeel. I built Glass Page myself, with a lot of feedback from friends and the people I work with.
It started with a system design doc. My agent wrote it, and I wanted my team to comment on it. Pasting it into chat lost the formatting, screenshots lost the context, and the feedback ended up spread across chat and email with no easy way back to the agent.
Now Claude, ChatGPT, Cursor, Codex or any agent on MCP can publish what it makes as a Pane with a link. Your team leaves Comments right on the part they mean, in Threads. New Comments and replies show up as they come in. The agent reads them, makes the changes and publishes a new Version. The Latest Link always shows the current one, so nobody reviews an old copy.
You can also publish a Canvas. The Pages are laid out on one link, and people pan and zoom a flow or a set of screens. Press P to hide Pins. You can post a Review on a Version, including on your own Pane.
Star a Pane to keep it at the top of your lists, and filter to the ones you starred. Reload keeps your scroll position. I also fixed some issues on iPhone.
It's free for up to 10 Panes. Pro is $5 a month. Team is $8 a Seat a month. You can sign in with email or GitHub. Pricing is at glasspage.ai/pricing. To connect your agent, use https://mcp.glasspage.ai/mcp.
What would help me most:
I'll be around in the comments.
pinning comments to the exact spot is what makes review of a long doc workable. when the agent replies with a new version, can reviewers see what changed from the last one?
@neerajnathany Thanks, that's exactly the problem I kept hitting with long docs.
There's no side-by-side diff. What you get today: when the agent publishes a new Version, open Threads move with the part they're pinned to, and if that part changed, the Thread is marked Outdated so you know to look again. The agent replies in each Thread and resolves what it fixed, so you can work through the changes from the feedback itself. On a Canvas, any Frame that changed gets a "Changed in v4" marker.
Would a visual diff be the thing you'd reach for, or is following the Threads enough for how you review?
the comment ending up 40 messages away from the paragraph it was about is exactly what happens when agent docs get pasted into chat
when the agent picks up a Thread, does it know which Version the comment was left on??? if two pepole review different Versions that feels like where it gets messy
@thamibenjelloun Yes. Every Comment records the Version it was left on, and the agent's tools return it, so the agent always knows which Version a Thread is about and exactly where on the page.
Two people reviewing different Versions is fine. Each Thread stays on its own Version, marked with it, and the agent reads all of them in one go. When a new Version ships, open Threads whose spot still exists carry over, and if the content under them changed they're marked Outdated. The rest stay on the Version they were left on, and the Author gets a note linking to them, so nothing gets lost.
Most people just use the Latest Link, which always shows current work, but you can send someone a specific Version's link to review that one.
Curious if that matches how you'd want it to work, or if you've hit a messier case.
This is the gap I keep hitting. My agent writes a design doc or a chunk of code, I paste it somewhere for feedback, and the comments end up 40 messages away from the thing they were about. Pinning threads to the exact spot and keeping one Latest Link is the part that would actually get me to use it.
The missing piece for me is a visual diff between versions — if the agent regenerates the whole doc, I don't want to re-read it to find what changed. Does it handle code as well as docs, or is docs the main use case right now?
@jcbuilds Comments ending up 40 messages away from the thing they were about is exactly why I built this.
No visual diff yet. What you get today: pinned Threads follow their spot to each new Version, and if that spot changed they're marked Outdated, so you know where to look. On a Canvas, a changed Frame gets a "Changed in v4" label. And the agent usually opens a Thread on the new Version saying what it changed.
Docs, reports and prototypes are the main use right now. Code works if your agent shows it as a page, and then you can pin a Thread to exact lines.
Launched yesterday, already five fixes in. Reviews now resolve cleanly from the newest Version, following holds up across tabs, and shared Panes land in your own Workspace instead of cluttering a team list. What would you want it to do next? Tell me the feature you'd reach for, I'm reading every comment.
latest link always showing the current version is so thoughtful. congrats Nabeel!
@mohitvishwakarma I'm glad you found it useful! Try it out and let me know how it goes. I'm always open to feedback.
@exabyt3 will do, rooting for you Nabeel
This makes it much easier to share AI-generated work and get feedback without jumping between different apps. Congrats.
@spotch_founder Thanks! Hope you find it useful and I am always open to feedback.