I had trouble getting superpowers-chrome to work inside of a packnplay container. I coached claude to make use of chrome in the host environment. Eventually cc patched the plugin code directly. Here's what it did:
- replaced localhost with host.docker.internal
- add a "Host: localhost:9222" to all requests
I have to launch chrome in the host using the following command:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--remote-debugging-port=9222 \
--user-data-dir=/tmp/chrome-debug
It patched web socket URLs as well but I have no idea if that actually worked.
I don't have time at the moment to work through a PR but may work on it some other time, documenting this here for others in the meantime. I could envision other approaches working here as well, I'm not convinced this is the most elegant approach.
I had trouble getting superpowers-chrome to work inside of a packnplay container. I coached claude to make use of chrome in the host environment. Eventually cc patched the plugin code directly. Here's what it did:
I have to launch chrome in the host using the following command:
It patched web socket URLs as well but I have no idea if that actually worked.
I don't have time at the moment to work through a PR but may work on it some other time, documenting this here for others in the meantime. I could envision other approaches working here as well, I'm not convinced this is the most elegant approach.