Comments stuck to the component, not the ticket

The problem

Design feedback in a ticket loses the place on the page it was about.

Who would pay for this?

Product teams reviewing a staging site together.

How could it make money?

A possible model is freemium. That is an editorial guess from the shape of the launch, not a published price, and not evidence that komo uses it.

What would the MVP look like?

A script that lets a teammate comment on an element and reply in place.

Product that inspired this idea

Comments on a live site that stay attached to the component and the page, so a teammate can reply in place.

Posted by @tjcages. Launch page. No separate product site is listed unless the post itself is the source.

• comments
• web

Related startup ideas

• A browser inside the coding agent’s terminal

  Open a real browser from the agent session so the agent can see the page it just changed.

• A coding agent that runs a small model in the browser

  A coding assistant that runs locally in the browser on a small model, for people who will not send the repo out.

• A desktop for making games with the model you already pay for

  A local app that turns a Claude or ChatGPT subscription, or a local model, into a game-making bench.

• A full computer for an agent, not just a shell

  Rent a virtual machine with a desktop and a browser when the agent has to use real software.

• A live visual inside the coding thread

  Let an agent answer with a working visual, not only text, when the task is about an interface.

• A rich-text editor you can install in one command

  Ship a styled editor that matches the rest of a component library, instead of theming a blank one for a week.

More developer tools ideas