Browser Profiles in BAS

A profile is what makes a BAS bot remember who it is. Without one, every run starts as a blank stranger and has to log in again. With one, the account behaves like a returning user on a stable device — which is exactly what multi-accounting needs.

What a profile actually stores

By default BAS drives a Chromium browser, and its profiles work just like profiles in ordinary Chrome — they’re even compatible with Chrome profiles. A profile is a folder where the browser keeps everything tied to a session:

• cookies
• cache saved from site pages
• localStorage
• installed extensions
• history and other session data

Because all of that lives in one folder, the profile preserves your authorisation on sites — load it again and you’re still logged in, with no need to re-authenticate.

Permanent vs temporary profiles

BAS gives you two kinds, and the difference is whether state survives the run.

Permanent profile. Create or switch to a permanent profile points the browser at a folder path. If the folder doesn’t exist, BAS creates it and stores the cookies, cache, localStorage and so on there, building a full portable browser profile. If the folder already exists, the browser loads the profile data back out of it. By default this action also loads the profile’s proxy and device fingerprint — so the whole identity comes back together. This is what you use for any account you’ll return to.

Temporary profile. Switch to a temporary profile is the default in record mode when nothing else is specified. Each time, a new temporary profile is created and then discarded. Use it for one-off tasks where you explicitly want a clean slate with nothing carried over.

Managing profiles

• Copy profile to another folder — duplicates the current profile to a path you specify. It only works correctly if the profile isn’t currently in use by a thread, so copy it while idle, not mid-run.
• Get current profile info — reads details about the profile the thread is on.
• Delete profile — removes a profile folder you no longer need.

One profile per account

The rule that ties this to the rest of your identity stack: each account gets one permanent profile and keeps it. A returning user has a stable device and a persistent session. Bind the profile together with its proxy and its fingerprint, reuse the same trio every run, and the account reads as an ordinary human coming back — not a fresh bot logging in cold each time. Mismatched or constantly-reset profiles are exactly the inconsistency anti-bot systems look for.