The workflow this is pointing at is going to be everywhere eventually.
Right now I context-switch constantly. see something online that
sparks an idea, open a terminal, explain the concept to CC, lose
half the original context in translation. The interesting version of
this is: snapshot whatever caught your attention, explain what it
triggered, get a working prototype back without ever leaving the tab.
The local bridge approach makes sense for now. Curious how it handles
latency on larger DOM trees -- that's usually where these tools start
to feel clunky. Will try it.
This has been in my list for a long time, finally got time to pull it out.
Allows you to invoke Claude Code directly from a browser tab, inspect, modify the site on the fly, or using the mapped sources. Works on any tab and any website, multi session, history support, full DOM element selection support.
The workflow this is pointing at is going to be everywhere eventually.
Right now I context-switch constantly. see something online that sparks an idea, open a terminal, explain the concept to CC, lose half the original context in translation. The interesting version of this is: snapshot whatever caught your attention, explain what it triggered, get a working prototype back without ever leaving the tab.
The local bridge approach makes sense for now. Curious how it handles latency on larger DOM trees -- that's usually where these tools start to feel clunky. Will try it.
Claude Code In The Browser.
This has been in my list for a long time, finally got time to pull it out.
Allows you to invoke Claude Code directly from a browser tab, inspect, modify the site on the fly, or using the mapped sources. Works on any tab and any website, multi session, history support, full DOM element selection support.
https://chromewebstore.google.com/detail/claude-code-browser...
Free to use.