dsh-platform-account-manager-plugin

Agents can already drive browsers, yet most projects stall on the same gap: which account to use, which data directory to open, and which backend to reach once the browser is closed. dsh-platform-account-manager-plugin turns that uncertainty into a deterministic mapping. A platform name plus an account name uniquely identifies a backend, bound to a Chromium data directory that can be isolated per account or shared across trusted platforms. The user logs in manually once; from then on Chromium restores the local session on its own.

The plugin centers on the full account lifecycle. Directory-level isolation and process-level sharing are selectable per business need. Session cookies are synced back into the original directory over a loopback CDP channel while the browser is online, without ever being exported into metadata. Login-status detection observes only URL redirections-no DOM reads, no clicks, no credential entry. A built-in keep-alive scheduler supports configurable intervals, random jitter, daily windows, and exponential backoff on failure. On the Agent side just four minimal tools are exposed (list, open, check-login, close), and none of them reveal directory paths, CDP endpoints, cookie values, or credentials. Independent browser-automation plugins obtain a trusted loopback CDP connection through ctx.platformSessions, keeping the permission surface small and auditable.

It is built for individuals and teams running multiple e-commerce, ad-tech, ERP, support, or content backends inside DSH, and specifically for those who want account management cleanly separated from generic page automation, a predictable browser process lifecycle, and directory ownership that can be archived, audited, and safely removed. It is not a password manager, not a general-purpose automation tool, and it does not bypass platform risk controls-its job is to hand the Agent a stable, identifiable, reusable session entry point before the backend is opened.