Agentforce Vibes IDE

Hi Trailblazer Community, 

I’m looking for clarification on the transition from legacy Code Builder to Agentforce Vibes IDE, specifically for production-launched Code Builder environments. 

In my production org, I can still navigate to the Code Builder Dashboard and launch Code Builder. The dashboard shows the retirement warning stating that legacy Code Builder support ends April 14, 2026, and that users should begin transitioning to Agentforce Vibes IDE. 

However, when I launch Code Builder from production, the IDE that opens appears to already be the Agentforce Vibes IDE experience. The UI includes Agentforce Vibes branding, MCP servers, Agentforce Vibes walkthroughs, and Salesforce DX tooling. I can also see my Salesforce DX project structure, including LWC metadata under force-app/main/default/lwc. 

When I run sf org display, the target org is my production org. 

My question is: 

After legacy Code Builder support ends, will Salesforce still support launching a full Agentforce Vibes IDE workspace from a production org, or will production users be expected to use Web Console for production investigation and use Agentforce Vibes IDE only from sandbox / Developer Edition orgs? 

The reason I’m asking is that my workflow includes both production investigation and LWC development/inspection. Web Console appears useful for SOQL, logs, Anonymous Apex, and production-safe code inspection, but it does not seem like a full replacement for a project-based IDE workflow involving LWC files, metadata, Salesforce CLI, and multi-file development. 

I’m trying to understand the intended future-state workflow for users who currently rely on production-launched Code Builder for: 

• inspecting production-connected metadata
• reviewing LWC files
• running Salesforce CLI commands
• querying production data for troubleshooting
• validating behavior against production records
• then building/testing changes safely in sandbox

Is the current production-launched Agentforce Vibes-style IDE experience expected to remain available after the legacy Code Builder cutoff, or is the supported path moving to: 

• Web Console for production investigation
• Agentforce Vibes IDE for sandbox / Developer Edition development?

Any clarification on the supported post-retirement workflow would be appreciated.

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!