Launch authenticated orgs
Open Salesforce CLI authenticated orgs directly from Chrome without manually running `sf org open` every time.
Chrome Extension + Native Companion
Open the right Salesforce org in seconds.
Salesforce CLI Org Launcher turns your local Salesforce CLI auth list into a clean, searchable Chrome launcher built around projects, favorites, and saved groups. No more digging through long terminal output when you just want the right org now.
Project-first workflow
See orgs in the context of the projects you actually work in.
Local-first design
Uses Chrome storage and a local native host instead of sending org data away.
Built for real teams
Save favorites, create groups, and keep your setup ready across extension opens.
A focused popup UI that surfaces authenticated orgs quickly, lets you search across aliases, usernames, project names, instance URLs, and org IDs, and opens the selected org in a new Chrome tab.
What the extension does
This is the full extension experience, not just a helper script. The browser extension, service worker, and native companion work together to give Salesforce developers a reliable launcher around their existing CLI setup.
Group by project
See orgs grouped around local project roots so the popup matches how you actually navigate development work.
Search everything fast
Search aliases, usernames, project names, instance URLs, and org IDs from one compact launcher without losing keyboard focus.
Favorites and custom groups
Save favorite orgs and create your own persistent groups for clients, releases, environments, or teams.
Settings that stay saved
Project roots, theme, auto-refresh, cache duration, expanded sections, and groups are stored locally in Chrome.
Graceful expired-org handling
Status badges identify connected, expired, and unreachable orgs. Users can reauthorize from the card instead of guessing.
Setup and auth actions
Open Salesforce Setup, authorize a new org from Settings, or remove a local CLI auth entry after confirmation.
How it works
Chrome Web Store installs the extension. The local companion host is installed once per machine so Chrome can securely communicate with Salesforce CLI through native messaging.
1
Install the extension
Install Salesforce CLI Org Launcher from Chrome Web Store once the listing is live.
2
Install the companion
Run one Node.js command. It detects macOS, Windows, or Linux, installs the right package, and smoke-tests Windows CLI detection.
3
Refresh and launch
Open the extension, click Refresh, and launch orgs directly from the popup UI.
Downloads
Most users can install with one command. The manual packages remain available for managed distribution and offline setup. These installers target the published extension ID nmjgfcdchchicaophfglfeijceibpkde, include compatibility allowlist entries for prior launcher builds, save the install-time PATH on Windows, avoid brittle absolute .cmd shim calls, and recover from stale Salesforce CLI web-auth processes on OAuth port 1717.
npx --yes github:kiranvm143/salesforce-cli-org-launcher-service-worker install
Companion package
Install the local native host for macOS or Linux with the included shell script.
One-click installer
Install the local native host on Windows with the ready-to-run setup app.
PowerShell package
Use this ZIP for portable, offline, or managed PowerShell installation.
One-click EXE source
Build SalesforceCliOrgLauncherCompanionSetup.exe on Windows with Inno Setup 6.
What users will see
The extension is designed to feel practical and fast: launcher first, settings close by, and setup guidance available when the CLI or native host needs attention.
Persistent custom groups
Create your own group structure and keep it available the next time the extension opens.
Settings built for real environments
Configure project roots, cache duration, auto-refresh behavior, and theme preferences from one place.
Clear setup guidance
When the CLI or companion is missing, the extension gives users concrete next steps instead of dead buttons.
Good defaults, careful permissions
The extension is designed to stay local-first, rely on narrow permissions, and avoid broad website access. That makes it easier to trust, easier to review, and easier to adopt across teams.
Privacy and permissions
The launcher is built around local productivity. It does not need “read and change all your data on all websites,” and it does not send Salesforce org metadata to the developer or third-party analytics systems.
Read the full privacy policy in the hosted privacy page or review the written version in PRIVACY_POLICY.md.