Skip to Content
VS Code ExtensionSettings

Settings

The extension contributes four settings under the sfdt.* namespace. All are workspace-scoped, so different projects can target different orgs and CLI binaries.

SettingTypeDefaultDescription
sfdt.cliPathstring"sfdt"Path to the sfdt CLI binary. Defaults to sfdt on your PATH; set an absolute path if the CLI isn’t found.
sfdt.defaultOrgstring""Org alias passed to commands via --org. Empty uses the project’s configured defaultOrg.
sfdt.dashboardPortnumber7654Port the sfdt ui dashboard server listens on.
sfdt.orgColorbooleanfalseOpt in to tint the VS Code window by org type (production = red, sandbox = orange, scratch/developer = green) to prevent wrong-org mistakes. When enabled it writes workbench.colorCustomizations into the workspace .vscode/settings.json; disabling it removes those keys again.

Example settings.json

{
  "sfdt.cliPath": "sfdt",
  "sfdt.defaultOrg": "dev-sandbox",
  "sfdt.dashboardPort": 7654,
  "sfdt.orgColor": true
}

If sfdt isn’t on your PATH (for example when using a Node version manager), point sfdt.cliPath at the resolved binary:

{
  "sfdt.cliPath": "/Users/you/.nvm/versions/node/v22.18.0/bin/sfdt"
}

Setting the org interactively

You can set sfdt.defaultOrg without editing JSON: click Select Org in the Status view title bar (or run SFDT: Select Org, sfdt.pickOrg). It lists your authenticated orgs from sf org list; pick one and it’s saved to sfdt.defaultOrg (workspace). Clear it (set it back to empty) to fall back to the project’s configured default org.

Last updated on
Embedded DashboardTroubleshooting