The daily toolkit for Salesforce developers: deploy a single file or a whole delta, validate a change before it lands, run Apex tests, rotate pipeline credentials, and export Confluence documentation to Markdown, all from inside the editor rather than the terminal. Problems are caught before they ever leave the developer's machine.
Lists every authenticated org. Click the swap icon to set the active one. The active alias shows in the status bar, so you can switch without opening the panel.
Shows the delta since the last deployed/<env> tag, or HEAD~1 if there is no tag yet. Right-click any file to deploy it on its own.
Deploys the file open in the editor to the active org. Prompts for Deploy or Validate. Best for iterating on one component.
Finds everything changed since the last deployed/<env> tag and sends it all in one go, so nothing is missed.
Right-click a file or folder in the explorer to deploy that path. Handy for pushing a whole feature folder at once.
A sidebar panel that exports any Confluence space to structured Markdown. No Python, no external tools: it runs inside the extension as a 4-step webview wizard, and you choose exactly which pages to export from a collapsible tree before it starts.
A panel in the Salesforce Dev Tools activity bar. Click the icon to open the wizard. The API token is saved to VSCode's encrypted SecretStorage and pre-filled next time. The destination folder is cleared before each run so stale pages never pile up.
The commands above cover the daily loop: deploy, validate, test. The palette goes further, with org switching, coverage checks, metadata retrieval, manifest generation and the rest of the pipeline setup commands.
| Command | What it does |
|---|---|
| SF Dev: Switch Active Org | Quick pick across all authenticated orgs |
| SF Dev: Deploy Current File to Org | Deploys the open file, prompts Deploy/Validate |
| SF Dev: Deploy to Org | Right-click file/folder, prompts Deploy/Validate |
| SF Dev: Deploy Changed Files (Delta) | Changed since the deploy tag, prompts Deploy/Validate |
| SF Dev: Validate Deploy (Check Only) | Check-only run of the whole force-app directory |
| SF Dev: Run All Apex Tests | Runs all local tests; results in the output panel |
| SF Dev: Run Apex Tests for Current File | Runs the test class matching the open file |
| SF Dev: Check Test Coverage | Reports org-wide and per-class Apex coverage |
| SF Dev: Retrieve Metadata from Org | Pulls metadata using retrieve.xml or force-app |
| SF Dev: Set Up CI/CD Pipeline | Full pipeline setup wizard (works with Pipeline Manager) |
| SF Dev: Add Pipeline Environment | Adds an org/branch without touching YAML |
| SF Dev: Rotate Pipeline Credentials | Refreshes expired SFDX Auth URLs: automated via API for GitHub, Bitbucket and GitLab, guided manual update for Azure DevOps and Jenkins |
| SF Dev: Enable Bitbucket Pipelines | Turns on Bitbucket Pipelines via REST API |
| SF Dev: Generate package.xml | Runs sf project generate manifest on the source directory |
| SF Dev: Initialise Deploy Tag | Creates deployed/<alias> tags at HEAD to set the delta baseline |
| SF Dev: Export Confluence Space | Opens the 4-step Confluence export wizard |
The safe habit the tooling encourages: prove every change against a real Salesforce org before anyone else sees it.
Edit Apex, LWC, flows or any other Salesforce metadata in the editor as usual.
Choose Validate (check-only). The org verifies the deployment without saving anything.
Check the SF Dev: Delta Deploy output channel and fix anything it flags before the change goes any further.
Once validation passes, commit. The CI/CD pipeline runs the same deployment against the target environment.
The initial release shipped the core deploy, validate and test commands. What followed landed inside a week: a deploy-mode picker, the pipeline setup and credential commands, then Confluence export and its refinements.
Confluence Export improvements: 4-step wizard with a page-selection tree (Select All / Deselect All), clear-before-export to drop stale pages, attachment CDN redirects followed, saved token accepted at validation, and esbuild bundling to keep node_modules out of the VSIX.
Confluence Export: 3-step webview wizard exports any space to Markdown with images. Encrypted token storage, HTTPS enforcement, SSRF protection.
Add Pipeline Environment, Rotate Pipeline Credentials, Enable Bitbucket Pipelines, Generate package.xml, Initialise Deploy Tag.
Pipeline setup wizard: auto-fetches auth URLs, registers them via the provider REST API, and writes the pipeline files and scripts.
Deploy mode picker on every deploy command: Deploy or Validate (check-only).
Initial release: Connected Orgs panel, Changed Files panel, status bar, and the deploy / validate / test / retrieve commands.