Agentforce Vibes IDE

Configuring Agentforce Vibes - My Experience

My company just licensed Agentforce Vibes for me and this is my configuration experience steps. 

In production, going to Setup "Agentforce Vibes IDE" now says "Agentforce Vibes is Now Native to Your Org" with no information for how to configure it. 

There's no help on the page and the "Trailblazer Community" link opens the community, but the sidebar information isn't for Agentforce Vibes, but for "Code Builder".  

I should mention I was using the preview version before it became licensed so I already had the extension installed.

Going to 

https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-overview.html, the configuration steps were not matching what I was seeing in my environment for configuring things. 

Here's the steps I did that successfully configured Agentforce Vibes in my production and sandbox environments. You might consider these steps a quick start. 

Production

1. Log into production Salesforce.
2. Go to Agentforce Vibes target Users and add the "Agentforce Developer and Admin Tools" Permission Set.
3. Open a Visualforce Project hooked to production.
4. Open the "Agentforce Vibes" panel in the left side bar.
5. At the bottom of the opened panel, hit the "Recheck" button.
6. The Agentforce Vibes panel shows directions that it is ready to accept input.

Sandbox

1. Log into a sandbox
2. In Settings, go to "Company" and click the "Match Production Licenses".
3. Wait for the email confirmation.
4. When the confirmation is received, go to Agentforce target Users and add the "Agentforce Developer and Admin Tools" Permission Set.
5. Open a Visualforce Project hooked to the sandbox.
6. Open the "Agentforce Vibes" panel in the left side bar.
7. At the bottom of the opened panel, hit the "Recheck" button.
8. The Agentforce Vibes panel shows directions that it is ready to accept input.

I hope this helps!

Following up on my recent blog post

 on Web Console, I wanted to address a few great questions that came up. 

Web Console vs. Agentforce Vibes IDE

A simple way to think about it:

• Web Console = lightweight, instant-on browser development
• Agentforce Vibes IDE = full cloud IDE with a full compute environment

What Web Console is

• A browser-based IDE embedded directly in Salesforce
• Built for fast, in-context tasks without leaving the org
• Available in all orgs, including free orgs
• Best for:
  • running SOQL
  • checking debug logs
  • using Anonymous Apex
  • making targeted Apex edits
  • validating a fix quickly
• In production, Apex is read-only for safety
• In non-production, you can make inline edits and save changes

What Agentforce Vibes IDE is

• A full web-based IDE that brings the power of VS Code into the browser
• Available in Professional Edition, Unlimited Edition, Enterprise Edition and Developer Edition
• Includes:
  • Salesforce Extensions
  • Salesforce CLI
  • GitHub integration
  • Agentforce Vibes extension for AI-powered development
• Best for:
  • larger projects
  • multi-file changes
  • source-driven development
  • AI-assisted coding
  • broader team/dev workflows

Biggest difference

• Web Console is optimized for proximity to the org
  • launch from Salesforce
  • stay in context
  • investigate → fix → validate fast
• Agentforce Vibes IDE is optimized for depth
  • full project workspace
  • richer tooling
  • better for sustained development work

Strengths of Web Console

• Loads fast and keeps you in the flow
• Great for troubleshooting and quick fixes
• Designed around common “something broke” workflows
• Lets you move from issue to code faster because it is embedded in Salesforce surfaces like Setup and org-aware workflows

Strengths of Agentforce Vibes IDE

• Full-featured browser IDE
• Better for building complete solutions, not just investigating issues
• Supports CLI, GitHub, AI workflows, and testing/deploying against scratch orgs, sandboxes, and Developer Edition orgs

Use Web Console when…

• you are already in the org and need to peek under the hood
• you want to run SOQL or inspect query behavior
• you need to review logs
• you want to make a small, targeted fix
• you want to inspect code in production safely
• speed and context matter more than a full dev environment

Use Agentforce Vibes IDE when…

• you are doing feature development
• you need a full IDE experience
• you are working across multiple files/components
• you need CLI, GitHub, or AI-assisted development
• you are working in a source-driven team workflow

Takeaway

• Use Web Console for quick, in-context investigation and edits
• Use Agentforce Vibes IDE for full-fidelity development

Developer Console will continue to coexist with Web Console for now, so this is not a sudden transition. Our goal is for Web Console to become the modern way to handle the quick-debug, query, and edit workflows developers have long used Developer Console for. If a key workflow is missing, that feedback is exactly what we want.