Introducing Inspector's context-aware screenshot tool! Screenshots as context for your coding agent is a pain. I decided I was tired of it and shipped something today to help with that.

Nov 8, 2025 · 5:49 AM UTC

Replying to @mkliku
Very cool! Are you all considering making the DOM available to the agent with something like Chrome DevTools MCP and linking to the node (instead of screenshotting)?
Hi Mauricio! We have a tool that allows you to select an element in the DOM and add the associated line of code in your codebase as context for the agent. Demoing that today!
1
Replying to @mkliku
looks fire
All about the little things
1
Replying to @mkliku
Love the demo!
1
1
Uhhhh 😳😳😳
3
Replying to @mkliku
sick!
1
1
Replying to @mkliku
Great demo man
1
2
Thanks man! W parrot
1
Replying to @mkliku
Hi Mike, this is really cool. How can I play with this more? I'm super keen on this space too!
1
1
Replying to @mkliku
That’s hella sick! Looking forward to try it out
1
1
Dude excited to Collison install for you 😏
Replying to @mkliku
slay mike
1
1
Replying to @mkliku
Joined the waitlist, but I am still trying to figure out what Inspector does. How is it different from Cursor or Windsurf? Is it only for the front end?
1
1
Hey Sachin! Totally right. Cursor/Windsurf are general purpose. Inspector is built specifically for front-end.
1
Replying to @mkliku
the demo is awesome mike!!
Thank you!!
1
Replying to @mkliku
smooth like 🧈
1
1
🤧🤧🤧 like criminal undercover
1
Replying to @mkliku
This is dope 🔥
1
1
Duuude I’m saying
1
Replying to @mkliku
dope platform mate! screenshot as context is smart, you capture visual locality need to try ~ feel free to push your tool/inspector to microlaunch.net whenever it helps btw
1
Replying to @mkliku
Nice! Screenshots can be such a hassle.
1
Replying to @mkliku
so smoooooth