What about having an intermediate server running on the same box as the browser, that connects to CDP using a pipe, and forwards messages to the Redis server, instead of modifying Chrome s source ? It's painful to maintain Chrome patches.
Really cool project in any case, seems like working at Pikkit must've been a lot of fun ! Thanks OP for sharing.
I know it's semantics, but I think it's important in this case to mention that the entire article is about the open-source Chromium browser, not the proprietary Google Chrome one.
Thank you! I thought people might know it more as Google Chrome. Hence why I changed it on the HN title. But the original blog title specifically mention Chromium.
What about having an intermediate server running on the same box as the browser, that connects to CDP using a pipe, and forwards messages to the Redis server, instead of modifying Chrome s source ? It's painful to maintain Chrome patches.
Really cool project in any case, seems like working at Pikkit must've been a lot of fun ! Thanks OP for sharing.
Not the OP but I’ve been thinking to write exactly this as part of making my personal browser available over MCP.
Chromium*
I know it's semantics, but I think it's important in this case to mention that the entire article is about the open-source Chromium browser, not the proprietary Google Chrome one.
Thank you! I thought people might know it more as Google Chrome. Hence why I changed it on the HN title. But the original blog title specifically mention Chromium.