Howdy Product Hunt! 👋
I’m Ekhtiram, the solo writer of Vibeocus.
Like a lot of you, I’ve been closely the use of AI brokers (Cursor, Claude Desktop, Claude Code) to construct internet apps in recent years. The execution pace is fantastic, however I repeatedly hit a large friction level when operating at the frontend.
Each and every time a UI component broke, or validation did not paintings, I needed to take a screenshot, open the browser check up on device, manually reproduction the uncooked HTML/CSS snippet, transfer to my AI device, and kind an extended instructed explaining *what* and *the place* the problem used to be. It utterly destroyed the “vibe-coding” momentum.
I sought after a approach to bridge my reside browser frontend without delay to my AI’s mission reminiscence. That’s why I constructed Vibeocus Lens.
Now, as a substitute of losing time copy-pasting, you’ll be able to simply click on any component for your web page, upload a snappy annotation, and Lens robotically extracts the precise DOM nodes, semantic CSS selectors, and visible state. It then streams the whole lot by the use of a safe native bridge without delay into your Vibeocus mission workspace, making it straight away obtainable on your AI equipment over MCP. 100% native, no cloud backend, 0 RAM hogging.
Amusing reality: You’ll in reality check the core extension UI reside proper on our touchdown web page with out even putting in it but!
I’m right here all day and would completely love your truthful comments. How do you presently maintain feeding UI/frontend context on your AI equipment? What options must I upload to Lens subsequent?
Let’s chat within the feedback! 🚀
