Comparison
How Inspekt differs from peer click-to-source devtools.
| Inspekt | LocatorJS | code-inspector-plugin | react-grab | |
|---|---|---|---|---|
| Click element → open IDE | ✅ | ✅ | ✅ | ✅ |
| Source snippet in overlay | ✅ | ❌ | ❌ | ❌ |
| Source-map fallback | ✅ (opt-in) | ❌ | ❌ | ❌ |
| Capability-aware toolbar icon | ✅ | ❌ | n/a (no extension) | ❌ |
| Multi-framework AST transform | ✅ (via code-inspector) | ✅ (own plugins) | ✅ | ❌ (React only) |
| Zero-config React via fiber | ✅ (via bippy) | ✅ | ❌ | ✅ (via bippy) |
| Chrome extension | ✅ | ✅ | ❌ | ✅ |
| MCP server for agents | ✅ | ❌ | ❌ | ❌ |
| Cross-app config sync | ✅ | ❌ | ❌ | ❌ |
Setup CLI (npx @aylith/inspekt setup) | ✅ | ❌ | ❌ | ❌ |
| Maintained 2026 | ✅ | dormant | ✅ | ✅ |
What Inspekt reuses
Inspekt deliberately doesn't reinvent the wheel:
@code-inspector/core— AST transformsbippy— React fiber traversalreact-grab— runtime primitives (freeze, context, open-file)launch-editor— IDE launcher@jridgewell/trace-mapping— source-map resolution@modelcontextprotocol/sdk— MCP server scaffoldinghono— daemon HTTP routing
Inspekt's unique surface area is the layer on top of these: the agent-routing logic, the Chrome extension shell, the setup CLI, and the capability-aware icon. Everything else is well-trodden ground done by others.