It uses (by purpose) the same session though as the main Chrome instance.
But it should be possible to implement an option to use a separate session. This might even be much simpler than my current approach (which not only shares the session, it also uses the same Chrome process).
It uses (by purpose) the same session though as the main Chrome instance.
But it should be possible to implement an option to use a separate session. This might even be much simpler than my current approach (which not only shares the session, it also uses the same Chrome process).