what are the challenges with the Chrome extension path?
Playwright and selenium automate the browser itself, but with the chrome extension you need to use the context of the current browser.
I’m not an expert in browser automation so found it challenging moving from playwright to make it completely browser based.
What I did though is having a loop to send instructions from playwright.
For instance, I will open the browser, and then enter a loop to await for instructions (can be from event such as redis) to execute again in the same browser. But still, it’s based on the session instantiated by playwright.