Handling multiple isolated identities vs one shared browser state

[pencil20388-eng]

Clean idea — sharing existing logged-in state with an agent removes a lot of setup friction for single-account automation.

A question about the boundary of the approach. ego-lite shares one browser's state, which is perfect when the agent acts as you. But some automation workflows need the opposite: multiple isolated identities that must not share fingerprint, cookies, or IP — multi-store e-commerce, multi-account social ops, etc. Reusing one browser state there would actively link the accounts.

For that case there's a separate category of tooling (antidetect browsers like AdsPower and others) that gives each identity its own isolated environment, and exposes a CDP endpoint per profile so agents can still drive them via Playwright/CDP. I keep a resource on that side here in case it's a useful reference: https://github.com/pencil20388-eng/awesome-anti-detect

Curious whether isolated-identity workflows are in scope for ego-lite, or whether you see that as a deliberately separate problem from the shared-state model you're building.