SFDT for Salesforce (VS Code)

Drive the sfdt CLI from inside VS Code. This extension is a thin, fast UI over the CLI — it does not reimplement any logic, so it stays in lockstep with whatever version of sfdt you have on your PATH.

Published to the VS Code Marketplace as sfdt.sfdt-devtools (publisher sfdt, display name "SFDT for Salesforce"). Install from the Extensions view, or: code --install-extension sfdt.sfdt-devtools. The npm workspace package is named sfdt-devtools — the Marketplace requires an unscoped name, so it is not the scoped @sfdt/... form used by the other workspaces.

Features

The SFDT activity-bar container holds three views plus a status bar:

• Commands — a grouped tree of the entire sfdt command surface (30+ commands / 50+ subcommands) across six categories: Deploy & Release, Org Health, Quality & Analysis, Documentation, Data & Scratch Orgs, and Project & Tools. Click a command to run it in a dedicated SFDT integrated terminal — live, colored, streaming output, with interactive prompts supported. Destructive commands confirm first. Right-click any command to Run, Copy the exact sfdt … invocation, or Open docs on sfdt.dev. SFDT: Run Command… is a searchable quick-pick over everything.
• Status — the active target org (alias, instance URL, connection), the git branch, an Org Health rollup, and the installed sfdt/sf versions with an "update available" hint. Use the title-bar Select Org button to switch the target org from sf org list.
• Org Health — reads the latest audit, monitor, scan, and drift snapshots and shows each check's status, summary, and findings; click a check to re-run it. All views auto-refresh when a logs/*-latest.json snapshot changes.
• Embedded dashboard — SFDT: Open Dashboard runs sfdt ui and shows the full web dashboard in an editor tab (authenticated via the CLI's launch token). Follows the editor's light/dark theme and recovers automatically from dashboard port conflicts. SFDT: Open Manifest Builder opens the same dashboard deep-linked to the changeset-style Manifest Builder page (browse metadata, tick components, preview and save package.xml / destructiveChanges.xml).
• Per-org window theming — tints the window by org type (production = red, sandbox = orange, scratch/developer = green) to prevent wrong-org mistakes. Opt-in — enable sfdt.orgColor (it writes workbench.colorCustomizations into the workspace .vscode/settings.json; disabling it removes those keys).
• Status bar — shows the active org and the worst monitor/audit status.

New here? When the sfdt CLI isn't found or the project isn't initialized, the views offer a one-click Run sfdt init and links to the install docs.

Requirements

• The sfdt CLI installed and on your PATH (npm i -g @sfdt/cli), or set sfdt.cliPath to its location.
• A Salesforce DX project initialized with sfdt init.

Settings

Development

npm install            # from the repo root (workspaces)
npm run build:vscode   # build flow-core + bundle to dist/extension.cjs
npm run test:vscode    # unit tests (vitest)

The workspace is selected by path (-w vscode) rather than by package name, so these keep working regardless of the manifest name.

Press F5 in VS Code to launch an Extension Development Host. Package a .vsix with npm run package:vscode.

Acknowledgements

This extension bundles parts of @sfdt/flow-core. Some of them (the API name prefixes and the default AI prompts) are derived from SF Flow Utility Toolkit by Mark Jones (MIT). The notice and the full list of derived files are in THIRD_PARTY_NOTICES.md, which ships in the extension package.