Ten thousand scrape sessions, ten thousand cookie jars

You're running long-lived scrape sessions for ten thousand seller accounts on a marketplace. Each one needs its own session cookies, its own logged-in state, its own captcha-solved trust score with the site's bot detector. Mixing them in one browser destroys all ten thousand at once when one gets banned.

Each account gets its own container. Each container runs its own Hoody Browser instance with a unique fingerprint and proxy. Cookies, local storage, the full session state lives in that container's filesystem. Idle, the container costs nothing: most accounts only need to be touched once a day.

When account #3,847 gets challenged, you /restart browser-1 in container-3847. The other 9,999 don't notice.

One container per identity, one URL per browser, one box for all of it.