Inspector
Figma for Claude Code
923 followers
Figma for Claude Code
923 followers
Inspector is a visual editor that connects to your favorite AI agent (Claude Code, Codex, Cursor). Click on an element in your UI, tweak it visually, and Inspector writes the change to your codebase. No more design handoff, just push to the repo.
Inspector
@boagworld Hey Paul! That's actually my fault, we've been shipping so fast the entire pricing flow is triggered from the desktop app. I'll be sure to add transparent pricing on the lander asap!
Here's the rundown:
Connecting Claude Code, Cursor CLI, Codex is always free
Free users get access to the same visual editing features as paid users
Paid users get access to more usage on Inspector Agent, which exposes GLM 4.7 (2x speed on Cerebras) as a model option
A paid subscription is $20/ month
Basically, the Inspector Agent is a way for us to provide $20 of free usage to people who would otherwise not connect their agent so that they can feel the magic. We're working on some really cool stuff that makes Inspector Agent even more powerful, so stay tuned!
Crow
This is super cool! How many people are using this?
Inspector
@jai_bhatia2 Thanks Jai! It's exciting to see so many new people trying it out and get feedback. Let me know your thoughts!
Autumn
Amazing tool, amazing team. Congrats on the launch!
Inspector
@ay_ush Thanks Ayush! We use Autumn for our usage tracking and we love it :)
Inspector writing changes straight to the codebase from a visual click is where this gets interesting. Most visual editors stop at generating a screenshot or a diff... actually resolving the element to its source line and pushing the edit removes the whole copy-paste-from-Figma loop.
Inspector
@piroune_balachandran Ayyeee yep that's the goal! Let me know any feedback have on the product!
Awesome stuff! Curious on what your long term goals are for Inspector! Do you expect visual-first editing to become the primary interface for frontend changes?
The "Figma for Claude Code" concept is interesting. Bridging visual editing and AI agents addresses a real gap in the design-to-code workflow.
I'm curious about multi-component scenarios: when a visual change affects multiple files (e.g., updating a shared component's layout that cascades to parent containers), how does Inspector handle the context propagation to Claude Code? Does it batch related changes or let the agent discover dependencies through the codebase?
Wow, Inspector looks amazing! That click & tweak to code workflow is seriously genius. How does it handle more complex UI interactions beyond simple style changes? Super curious!