From the command line
Requires Node.js 18 or newer.
npx my-provider-dash-manager
Run the same command later to update. The package also installs the short alias mpdm when installed globally.
Install · Windows 10 / 11
Install with npx if you already have Node.js 18+, or download the Windows installer straight from GitHub Releases. The installed app is a standalone executable; it does not need Node.js to run.
Two install routes
The command-line route downloads the newest installer from GitHub, verifies it is a real Windows executable, runs it, and launches the app.
SmartScreen will warn on the first run. The installer is not code-signed yet. Choose More info → Run anyway. Code signing is planned and removes the warning.
First run
Click Add account at the bottom of the rail, choose a service from the searchable picker, name the account, then choose Log in or Create a new account.
The real sign-in page opens in that account's own isolated session. Google services sign in directly. Elsewhere, prefer email/password or GitHub over “Continue with Google”.
Add every identity you need. Click a rail row or a tab to switch. Everything stays signed in. Optionally connect read-only tokens or import saved passwords.
Keep it current
Default. Checks on startup and hourly; downloads in the background; installs silently on close or on Restart & update. The rail badge turns into Restart to update x.y.z when it is ready.
npx my-provider-dash-manager — or mpdm update — updates an existing install silently and in place. Add --interactive for the wizard. Close the app first, or the running copy keeps the old version until restart.
Run the newest installer. It upgrades in place. Accounts, sessions, saved logins and settings live in %APPDATA%\multi-acc-manager and survive updates and reinstalls.
The CLI
Install globally with npm i -g my-provider-dash-manager to use the package name or the shorter mpdm alias anywhere.
| Command | What it does |
|---|---|
my-provider-dash-manager | Install or update to the newest release, then launch |
… install / … update | Install or update only |
… start | Launch the installed app |
… status | Installed version vs latest, plus where the app and your data live |
… where | Print the install and data paths |
… uninstall | Run the uninstaller (accounts and sessions are kept) |
Flags: --silent (no wizard on a first install), --interactive (wizard for an update), --download-only, --force, --version, --help. From a checkout of the repository, the equivalent is npm run install:latest.
Where things live
Windows 10 or 11 (64-bit). macOS and Linux are not supported yet. The architecture is cross-platform, so other operating systems remain future work.
About 350 MB with all tabs asleep, plus roughly 125 MB per live dashboard and about 2 MB per open account when dark mode is on. Eight GB of RAM handles the default five warm tabs comfortably.
The app installs per user under %LOCALAPPDATA%\Programs. Updates install in place.
Accounts, sessions, settings, plugins and encrypted logins live in %APPDATA%\multi-acc-manager. They survive updates and reinstalls.
The app is local-first: no telemetry, no sign-in to a service of ours, no cloud sync. The repository is public, so update checks need no token.
Developers can npm install then npm start. Smoke suites and release tooling are documented in the repository README.
If something sticks
Expected while the installer is unsigned. Choose More info → Run anyway. This is not a malware report; it is the absence of a signing certificate.
Google Cloud Console is a known case. Use the Browser button in the strip to open that page in your system browser. The rest of the app is unaffected.
Installed already?
Update to v0.8.0, or add the account you have been putting off.