Skip to Content
Chrome ExtensionTroubleshooting

Troubleshooting

Run the doctor

The fastest first step is the bundled diagnostic, which checks the bridge, the native host, the kill-switch file, and the telemetry snapshot:

sfdt doctor --extension sfdt doctor --extension --json # machine-readable sfdt doctor --extension --port 8080

Check the native host

sfdt extension status # which browsers have the host installed sfdt extension status --json

Inspect telemetry

sfdt extension stats # top features by activation count sfdt extension stats --json sfdt extension stats --limit 10

Console logging

Open DevTools on the Salesforce tab (Cmd/Ctrl+Opt/Alt+I → Console). The extension tags its messages with [SFUT]:

  • [SFUT] informational messages are expected (e.g. [SFUT] Shell mounted.).
  • Anything red is a regression worth reporting.

Common issues

SymptomLikely causeFix
Bridge feature says “Bridge not running”sfdt ui isn’t runningStart sfdt ui, then Test connection in options
”Test connection” failsWrong or stale tokenRe-copy ~/.sfdt/bridge-token; rotate it if needed and re-pair
A feature is missing from the menuIt’s toggled off, or kill-switchedCheck the options page; run sfdt feature-flags list
⚡ side button doesn’t appearYou’re not on a Salesforce page, or it’s inside a VF iframeThe button mounts only in the top frame of Salesforce pages
Native messaging not usedHost not installed for this browsersfdt extension install-host --extension-id <id>; verify with sfdt extension status
Major protocol mismatch warningExtension and CLI versions divergedUpdate both to the latest; see Bridge

Still stuck? Open an issue with the area: extension label at github.com/scoobydrew83/sfdt/issues .

Last updated on