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.
