Inspector - Edit your front-end, visually

What

Inspector is a local desktop tool for visually editing front-end codebases. It connects a coding agent to a browser-like interface so users can select elements on a page, move them, edit text, add comments, and apply those changes directly to the underlying code.

The product appears aimed at developers and designers working on front-end applications, especially React apps, who want a faster way to move between visual inspection and code changes. Based on the page, Inspector is positioned as a visual layer on top of a local codebase rather than a traditional browser or IDE, with support for agent-assisted workflows through Claude Code, Codex, and Cursor.

Features

• Visual element editing — Users can move elements visually and apply those changes so they are saved back to the codebase.
• Text editing in place — Double-clicking page text allows direct editing, which is then written to the underlying project files.
• Element-to-code linking — Inspector maps page elements to their exact line of code, which helps users understand where to make or review changes.
• Coding agent connection — It can connect to Claude Code, Codex, or Cursor accounts, supporting agent-assisted front-end workflows.
• Page-aware screenshots — The tool can capture screenshots that snap to specific page elements, which is useful for visual context and communication.
• Local-first workflow with GitHub publishing — Inspector works with local codebases and, according to the page, supports creating branches, committing changes, and publishing pull requests through GitHub.

Helpful Tips

• Validate framework fit early — The page states Inspector works best with React, so teams using other front-end frameworks should expect weaker visual-context mapping and test on representative projects first.
• Use it to shorten design-to-code loops — This kind of tool is especially useful when designers or PMs need to propose small UI changes without manually tracing component files.
• Check team workflow around local projects — Inspector is built around local codebases, so adoption will be smoother for teams already comfortable cloning repos and working from local environments.
• Review agent usage boundaries — Since the product connects to external coding agents, teams should define when visual edits are enough and when deeper code review is still needed.
• Note current platform limits — The page only mentions MacOS availability and says Windows is not yet supported, which may affect team-wide rollout.