THIS GUY ADDED A LIVE BROWSER TO CLAUDE CODE SO YOU CAN CLICK ANY ELEMENT AND EDIT IT INSTANTLY
@om_patel527K followers
154,329 views
31 Comments
Comments from the original post on X (Twitter)

@EliranTutia
Hey, I'm the creator. Really appreciate the shoutout 🙏 timing is wild - shipped a new version yesterday that adds flow recording, so you can capture a full click-through of your app for many purposes. Feedback and contributions are welcome
22 likes

@AlgoDolan
@grok analyze all information in the video above and find the official github repo
12 likes

@vladzima
the biggest time sink in claude code isn't the model thinking, it's me trying to explain which button i mean using prose. pointer beats paragraph every time
10 likes

@thePM_001
can do something like this but better. or you develop a proper AEP (agent element protocol) but you don't have intelligence for that.
3 likes

@Mr_Willis_T
Same thing, right?
3 likes

@Eric_M_Stevens
pointing at the thing you want to change is how humans have communicated since caves. describing it in text to an AI was always a weird detour
3 likes

@yesith_thomas
Isn't there a better version of this with @benjitaylor's Agentation? I feel like Agentation is more cleaner, open source and still gives way more context for comments to agents.
3 likes

@BuiltByLowe
That’s really smart. I’m juggling the idea of making something that extends Claude usage limits by working with the caching and token usage. Most people don’t know that if you don’t use Claude within five minutes of your last prompt, the next prompt it completely reloads its memory and all the code it’s looking at. So thousands of tokens are going to waste. Should I build it?
2 likes

@toms_dome
built lock in with claude - describing layouts killed 40% of my time. curious if the click accuracy beats text prompts tho
2 likes

@oricyberwolf
This fixes the biggest pain in vibe coding. Describe wrong = stuck.
2 likes

@nomophoneios
we are mass-producing senior frontend engineers in a weekend and agencies are still charging $150/hr for someone to argue about padding values in figma the gap between what one person can build alone and what a 10 person team ships is closing so fast it's actually terrifying for anyone whose entire business model is "we have more people"
2 likes

@Dazzaz
This is something that I'd love to have natively in ClaudeCode. @AnthropicAI
2 likes

@EndrewBiz
can't you do this too in the claude code preview section?
2 likes

@itsthedonhashim
@om_patel5 this is a game changer. finally more freedom to tinker and adjust on the fly without typing a single line
1 like

@dnsofmoney
Repo:?
1 like

@kingofheroesCM
Did someone test it?
1 like

@MoneyNomads1
been waiting for someone to do this. the gap between "I see the bug" and "I can describe the bug to the LLM" is where half my dev time goes. click-to-target kills it. open source is the cherry on top
1 like

@glass__ai
Glass has this built in for Claude as well as Gemini and GPT
1 like

@Argona0x
u won't believe how long i’ve been looking for this
1 like

@CChirchi
whoa that's genius!! no more selector hell
1 like











