The runtime DevTools platform for VS Code

Your frontend.Fully inspectable.

Inspectro is a VS Code extension that shows your components, renders, network and SSR execution while your app runs. The runtime your browser hides and your AI can't watch — right beside your code.

Version 1.0.1 islive on the VS Code MarketplaceInstall command:ext install hemasai.inspectro
inspectro · inspectorCONNECTED
Inspectro Inspector: component tree, live editable props and a highlighted preview
INSPECT.TRACE.DEBUG.UNDERSTAND.INSPECT.TRACE.DEBUG.UNDERSTAND.INSPECT.TRACE.DEBUG.UNDERSTAND.
INSPECT.TRACE.DEBUG.UNDERSTAND.INSPECT.TRACE.DEBUG.UNDERSTAND.INSPECT.TRACE.DEBUG.UNDERSTAND.
01 · In Action

Set a breakpoint in SSR. Sixty seconds.

One session, one editor: the component tree, the render, the request and the server-side pause that produced it.

Image
Coming soonInspectro: full product walkthrough
02 · The Problem

Modern frontends are too complex to debug from one place.

Every session becomes a relay race across eight disconnected tools. Context evaporates between every switch, and the bug lives in the gap.

Context switching =Lost hours
01Browser DevTools

Your component names are gone: you're in <div> soup, hunting the React tree in another panel.

02VS Code Debugger

Breakpoints, but no component tree, no render counts, no network tied to a component.

03React / Vue DevTools

Framework tree in the browser, source in the editor. Two windows, no link between them.

04Coverage Reports

A separate HTML report you open once and forget, and not tied to the branch you're on.

05A11y Scanners

A CLI or browser add-on, findings dumped as a list, disconnected from the component at fault.

06Performance Profilers

Flame charts of frames, not render counts per component. You still guess which one.

07Env Switchers

Restart, re-login, re-seed. Every environment change costs you the session.

08Cookie Editors

A browser panel in yet another window, for a two-line change.

Unified by Inspectro
The AI question

AI writes it.You still have to see it run.

AI is blind once the app is running

It writes code fast and can guess at fixes, but it reads static source. It can't watch your SSR render, count your re-renders, or see the request that fired three components deep. And when AI wrote the code, you're debugging something you didn't even write.

Inspectro shows what actually happens

Real renders, real network, real breakpoints, real SSR execution: the ground truth the AI and the browser can't give you. Deterministic and local, and it runs against your own dev server, not a cloud.

Inspectro is the eyes.

AI is a planned optional add-on, never required
04 · VS Code Native

Your frontend,
right next to your code.

No tool-hopping across five windows all day. The component tree lives in the DevTools panel that opens in your browser, one click from its source in VS Code: source, runtime and breakpoints in one flow. One tool instead of five.

Questions

Before youinstall it.

Something not working once you’re running it? The docs have a troubleshooting section
.

05 · Get Access

Be first inside
the telescope.

Install the extension and sign in to get started, or reach the team directly using the form below.

01 / Who you are

02 / What you need

03 / Your setup

What do you do?

How big is your team?

Primary framework

0 / 120 minimum

Not ready to send. Still needed: your name, your email, your message.

Goes straight to the team. One person reads it.