Quickstart
This walkthrough takes a freshly-authenticated Salesforce DX project from nothing to a
validated deploy. It assumes you’ve installed the CLI and the
Salesforce CLI (sf).
Log in to an org
sf org login web --alias my-dev-orgInitialize SFDT
cd your-salesforce-project
sfdt initsfdt init is interactive. It writes a .sfdt/ directory containing config.json (org
aliases, coverage threshold, AI provider, feature flags) and a few companion files. You can
edit them later or with sfdt config set <key> <value>.
Run preflight
sfdt preflightPreflight runs a checklist of pre-deployment validations (git state, branch naming, tests,
changelog — whichever you’ve enabled). Use --strict to fail on warnings.
Run tests
sfdt testThe enhanced runner executes Apex tests in parallel and enforces your configured coverage
threshold (default 75%). Add --analyze to get an AI explanation of any failures.
Deploy
sfdt deploysfdt deploy runs preflight first (skip with --skip-preflight), deploys to your default
org, and can tag and open a PR. Use --dry-run to validate without deploying, or
--source-dir <path> to deploy a specific folder.
Smoke-test the deploy
sfdt smokePrefer a UI? Run sfdt ui to open the local dashboard at
http://localhost:7654 and run tests, preflight, drift, and compares
from your browser. See CLI → Web dashboard.
Where to go next
- Ship a release → Production release workflow
- Understand a failed deploy → Investigate a failed deploy
- Work inside Salesforce → Chrome extension
- Work in your editor → VS Code extension
- Full command list → CLI command reference