Browser profile management: organize accounts at scale.

A browser profile is a portable identity: a persistent user-data directory with cookies and session state, plus configured proxy and credentials, user agent and screen parameters, a deterministic fingerprint seed, and metadata such as groups, tags, and extensions.

Treat each profile as an asset with a lifecycle, not a disposable window. Everything below follows from that shift.

• Name by pattern, never by mood: client-platform-role, like acme-instagram-poster.
• Group by client or business unit; tag by platform, region, and status.
• One profile per account, forever. Sharing a profile between two live accounts is how clusters happen.
• Record the proxy assignment in the profile metadata so exit IPs are auditable.
• Duplicate, do not recreate: cloning keeps working settings and skips config drift.

The proxy belongs to the identity, so it belongs to the profile. Store HTTP, HTTPS, or SOCKS5 credentials inside each profile, run the preflight check to confirm the exit IP and country before logging anything in, and change a proxy only with a plan, because an account that suddenly logs in from a new country invites review.

A static residential IP per account is the dependable default; rotating exits suit scraping, not account lifetimes.

• One owner per profile at any moment; transfers are explicit.
• Sync through a workspace, not through exported files on a shared drive.
• Revoke devices the day someone stops needing them.
• Let concurrent-open warnings stop accidental double sessions.
• Use trash instead of hard deletes until offboarding is confirmed complete.

AliasMode’s free Cloud workspace covers exactly this loop: encrypted portable-profile sync with local caching, owner and member roles, device revocation, version-based conflict detection, and trash recovery.

Scripts should drive the same profiles humans use, so automation inherits cookies, fingerprints, and proxy history. AliasMode exposes a loopback Local API on 127.0.0.1:50400 to list and start profiles, returns a CDP URL that Playwright attaches to, and stops the browser cleanly when the job finishes. MCP servers extend the same control to AI clients.

1. Create: apply the naming pattern, group, tags, and proxy from day one.
2. Warm up: light, human-paced activity in a stable identity.
3. Operate: keep the profile frozen; change nothing but content.
4. Hand off: transfer ownership through sync, verify, then revoke the old device.
5. Retire: export an archive, remove access, and trash after confirmation.