Commands
The Commands view is a grouped tree of the entire sfdt CLI surface — 30+ commands and 50+ subcommands. Click a command to run it in a dedicated SFDT integrated terminal: live, colored, streaming output with support for interactive prompts (org selection, confirmations). Subcommands nest under their parent.
Categories
| Group | Commands |
|---|---|
| Deploy & Release | deploy, preflight, rollback, release, manifest, pr-description, changelog (generate / release / check), smoke |
| Org Health | audit (all + audittrail / licenses / mfa / unused-apex / inactive-users / api-versions), monitor (all + limits / errors / health), backup, scan, drift, doctor |
| Quality & Analysis | quality, test, Run LWC Tests (test --lwc), review, flow (scan / conflicts) |
| Documentation | docs (generate / diagram), explain, compare |
| Data & Scratch Orgs | data (list / export / import / delete), scratch (create / list / delete / pool status / pool fill) |
| Project & Tools | init, config, pull, Open Dashboard, mcp start, extension (status / stats), update |
The command palette and Commands tree also include CI pipeline generators for all four providers (GitHub, GitLab, Azure, Bitbucket) — monitor, deploy, release, and scratch workflow types.
Running, copying, and docs
- Click a command to run it in the SFDT terminal.
- Right-click any command for Run, Copy command (the exact
sfdt …invocation), or Open docs (the matching page on this site). - Search the whole catalog with SFDT: Run Command… (
sfdt.searchCommands) — it matches on label, description, and argv.
Destructive commands — deploy, rollback, backup, data delete, and scratch delete — prompt with a modal confirmation before running. Read-only commands run immediately.
Org targeting
When sfdt.defaultOrg is set (use the Status view’s Select Org
button), the extension appends --org <alias> to each command. When it’s empty, the CLI falls
back to the project’s configured default org (from .sfdt/config.json or sfdx-project.json).
How views refresh
The extension watches logs/*-latest.json and rebuilds the Org Health and Status views
whenever a snapshot changes — so running audit, monitor, scan, or drift (from the terminal
or anywhere else) updates the trees automatically.