Salesforce CLI Setup Guide
jSummer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Before You Begin
Release Notes
Move from sfdx (v7) to sf (v2)
Uninstall Salesforce CLI or Plugins
Run Salesforce CLI Using a Docker Image
Use the Doctor to Troubleshoot Problems
Error: Bad CPU Type
Where is Salesforce CLI Installed?
Error: Command Failed with ENOENT
Error After Installing Salesforce CLI on PowerShell Using npm
CLI Deprecation Policy
Next Steps
Newer Version Available
Troubleshoot Salesforce CLI
Here’s a list of Salesforce CLI errors and how to fix them.
-
Use the Doctor to Troubleshoot Problems
Quickly gather Salesforce CLI configuration data and run diagnostic tests with the doctor command. The main use case of the command is to easily generate information files that you can attach to GitHub issues or provide to Salesforce Customer Support. You can also use the doctor command to troubleshoot Salesforce CLI problems by interpreting the output yourself. -
Error: Bad CPU Type
You get the error Bad CPU type in executable when you try to install Salesforce CLI on macOS. -
Where is Salesforce CLI Installed?
When troubleshooting installation problems, it's often useful to know which directories Salesforce CLI is installed in. -
Error: Command Failed with ENOENT
After recently installing Salesforce CLI, you get this error when you run a command such as project generate. -
Error After Installing Salesforce CLI on PowerShell Using npm
After installing Salesforce CLI on Windows PowerShell using npm, you get a security policy error whenever you try to execute any CLI command. Installing with the Windows-specific installer works correctly.