
Introduction: Shift from Code to Intent with Agentforce
The era of Vibe Coding is here, and it’s a game-changer for Salesforce developers. Coined to describe the shift from writing boilerplate code to simply describing your intent in natural language, Vibe Coding lets you focus on high-level architecture and business logic. Your AI agent handles the heavy lifting.
Salesforce is leading this charge with Agentforce for Developers—the next evolution of their AI-powered developer tools, superseding the previously provided Dev Assistant. This new, more autonomous agent is designed to dramatically increase your productivity, allowing you to generate Apex, LWC, and other code with simple prompts.
But to truly unlock its full “agentic” power, you need to enable a specific configuration in VS Code. This step-by-step guide will walk you through setting up Act Mode and connecting to the necessary MCP Servers to get you Vibe Coding in minutes!
Prerequisites: Getting Your Environment Ready
Before you dive into the advanced settings, make sure your development environment meets these three essential requirements.
- Install Salesforce Extensions for Visual Studio Code:
- Ensure you have the latest Salesforce Extension Pack installed in VS Code.
- Create a Salesforce DX project and Authorize your Org to connect your local development environment to your scratch org or sandbox.
- Set Up Agentforce for Developers:
- Agentforce for Developers (which contains the Dev Agent) is included in the Salesforce Extension Pack and is often enabled by default. Confirm the extension is installed and active.
- Salesforce CLI Version V2.91.5 or Higher:
- The latest Salesforce CLI is crucial for interacting with the AI agent’s infrastructure.
- Run
sf updatein your terminal to ensure you have version V2.91.5 or higher.
The Vibe Coding Power-Up: Enabling Act Mode
The key to unlocking the full potential of the new Dev Agent lies in enabling its advanced Agentic Chat and debug logging. This setup is what allows the agent to reason, plan, and execute more complex, multi-step actions—the heart of Vibe Coding.
Follow these steps precisely:
Step 1: Open Your Settings File
In Visual Studio Code, open the Command Palette (usually by pressing Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on Mac) and search for:
Preferences: Open User Settings (JSON)
This will open your settings.json file.

Step 2: Add Agentic Chat Configuration
Add the following two lines of code to the existing content of your settings.json file. If there are other settings, ensure you place these in the correct JSON structure (e.g., separating settings with commas).
"salesforce.einsteinForDevelopers.enableDebugLogging": true,
"salesforce.einsteinForDevelopers.advanced": {
"enableAgenticChat": true
}
enableDebugLogging: A helpful setting for troubleshooting, ensuring you can see the agent’s full reasoning flow.enableAgenticChat: This is the critical flag that activates the agent’s advanced reasoning and planning capabilities.
Step 3: Access the Agentforce Panel
Save and close the settings.json file. Now, click on the Agentforce Icon in the Activity Bar on the left side of your VS Code window. This will open the Agentforce chat panel.
Step 4: Switch to Act Mode
Within the Agentforce panel, you will see an option to switch to Act Mode. Click this to change the agent’s operational state from a simple conversational assistant to a fully autonomous, action-oriented agent.
Step 5: Manage MCP Servers
In the same panel (or often available in the Agentforce view’s overflow menu), click the “Manage MCP Servers” option.
Step 6: Toggle On “Salesforce DX”
You will see a list of available Multi-Cloud Platform (MCP) Servers. Toggle On the server labeled “Salesforce DX”.
This final step connects your enhanced Agentforce for Developers to the core Salesforce DX tools and metadata, giving it the necessary context and permissions to perform developer actions directly within your project.

Conclusion: Start Vibe Coding Today
Congratulations! Your Agentforce Dev Agent is now fully configured for Vibe Coding. Instead of asking “How do I write an Apex trigger for X?”, you can now simply give the instruction: “Create a trigger on the Opportunity object to update the parent Account’s custom roll-up summary field whenever an opportunity is closed-won.”
This is the future of development—less manual labor, more architectural focus, and a significant boost in productivity. Start experimenting with complex natural language prompts and feel the vibe of faster, smarter Salesforce development!
Salesforce Aricle:
https://developer.salesforce.com/docs/platform/einstein-for-devs/guide/devagent-overview.html