Arguseye - See and verify UI edits in your coding agent or VS Code

by•
Preview React, browser-renderable Next.js and Vue components from source without starting the app. Give coding agents screenshots and baseline diffs, or inspect unsaved edits in VS Code. Missing inputs, warnings and errors stay visible.

Add a comment

Replies

Best
Maker
📌

Hi Product Hunt! I’m Ayush, the maker of Arguseye.

A coding agent can write a component and check its source, but a source diff doesn’t show the heading that wraps badly or the theme that failed to apply. I built Arguseye to make that feedback part of the editing loop.

Choose a component from your project. Arguseye renders its actual source with your installed packages, supported styles, and discovered usage props. Capture a baseline, edit the component, then inspect the before/after images, changed pixels, accessibility text, and new or resolved errors.

There are two ways to use it:

• Give your coding agent the MCP tools and bundled skill, or use the CLI.

• Open the VS Code extension to preview unsaved edits, choose a usage, and check mobile, tablet, or desktop widths.

It supports React, browser-renderable Next.js components, and Vue 3. These are isolated previews: runtime props, missing providers, and unsupported server behavior remain visible as incomplete context. A visual difference is evidence to review, not an automatic correctness verdict.

Arguseye is free to install, MIT licensed, and runs locally. This gallery uses frames from the launch film: demo components rendered by Arguseye and illustrated explanations of the workflow. The editor scene is an illustration, not a VS Code recording.

You can start from the website’s agent installer or the VS Code Marketplace link. Which component would you try first, and what evidence would help you trust an agent’s UI edit?