Troubleshooting

Agentforce Vibes uses large language models (LLMs) to generate output. Because LLMs don’t always produce perfect results, you may need to re-prompt or adjust your request when the output doesn’t meet your expectations.

If your company requires the use of a proxy, configure it through the Salesforce CLI rather than VS Code to ensure the Agentforce Vibes extension works correctly.
  1. Confirm that you have a Salesforce DX project open. Check that your workspace contains an sfdx-project.json file. See Salesforce DX Project Configuration.
  2. Confirm that the Agentforce Vibes extension is active. Run Developer: Show Running Extensions and look for Agentforce Vibes in the list.
  3. Confirm that you’re connected to a Salesforce Org with Agentforce Vibes enabled. The status of your default Org connection appears in the status bar.

Run SFDX: Open Default Org to quickly verify that your Salesforce extensions are running and that you’re connected to an Org.

If Agentforce Vibes fails to activate on Windows with no clear error, the Microsoft Visual C++ Redistributable may not be installed on your machine. Install the latest version from Microsoft’s download page, then restart VS Code.

Run these Salesforce CLI commands to diagnose the issue:

Check Salesforce CLI installation

Verify Org authentication

Check Node.js version

If the MCP server still doesn’t connect after verifying these, check the activity log in Settings > Logging for connection errors. See Debug Logging.

If your prompts get no response and the model selector shows no models, your user likely doesn’t have the required permission set license assigned. See Frequently Asked Questions.

If code suggestions are unexpected or inconsistent, another AI-enabled extension may be interfering. Disable all other AI-enabled extensions while using Agentforce Vibes. See Frequently Asked Questions.

To capture logs before filing a bug report:

  1. Open the Agentforce Vibes panel and click the Settings icon (⚙).
  2. Click Logging to expand the section.
  3. Toggle debug logging on.
  4. Reproduce the issue.
  5. Click Open activity log to open the log file. For model-level detail, click Open full trace.
  6. Enable Redact sensitive data before sharing the log file.

See Debug Logging for a full description of logging options.