I'm a Salesforce Consultant and I've had agentforce vibes connected and working in a multiple client orgs. Recently I'm randomly getting this error message when attempting to switch the org it's connected to.
e.services.ConnectionService.listAllAuthorizations is not a function
Hi Team,
Agentforce Vibes Extension is enabled in my org, and the Agentforce Vibes IDE is connected to my developer org. However, when I click on Agentforce Vibes in the IDE, it keeps loading and does not open the chat window, as shown in the attached screenshot. Please advise.
Hi @Suman Nuthalapati - Can you reinitiate the same again? Close and reopen. Also make sure that you have Agentforce, Einstein enabled
Hi Team,
Few questions on agentforce vibes IDE.
1. Is that not visible in production? I can see only in sanboxes
2. How to turn the visiblity off in sandboxes?
I want to disable in sandbox.
I have this turned off.
I still can see the agentforce vibes
Disable Extension
This will prevent the extension from being used when this org is the connected org in the IDE.
Thank you for adding the ability to install Code Builder in sandbox environments. This was critical for ensuring that we don't have developers accessing production environments.
What does the roadmap look like for dynamically handling IP restricted environments for Code Builder access? This is a big hurdle for us using the tool as we don't want to burden our admins with maintaining IP addresses for this.
thanks for your response. I'll just wait until it's rolled out.
Kr,
Gert
How to add my team shared project repo hosted on github to agentforce Vibes IDE as a remote repo.?
I want to checkout to the local feature branch in the local github repo and commit my features to that local feature branch. Then push those changes to the remote feature branch in remote team shared repo which is the same workflow most developers follow when using VS Code IDE installed on their desktops.
Create a Project from a Repository
has steps to clone an existing GitHub repo into your environment. While it references Code Builder, that has been renamed Agentforce Vibes IDE
You will need an SSH key that is recognized by GitHub to connect. Steps for
Connecting to GitHub with SSH are linked in the article as well.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:
What Web Console is
What Agentforce Vibes IDE is
Biggest difference
Strengths of Web Console
Strengths of Agentforce Vibes IDE
Use Web Console when…
Use Agentforce Vibes IDE when…
Takeaway
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.
@Ravi Grover Not sure what you mean. Tested it just now and I was able to open Web Console, go into Org Browser and retrieve all LightningComponentBundle in the org (LWC) and they opened correctly in the editor.
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:
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:
Any clarification on the supported post-retirement workflow would be appreciated.
Hello all!
I wanted to ask a question about how Agentforce Vibes can be used for testing.
I see there are many posts and training material on how Vibes can be used for quick developments and deploys, but haven't seen really any extensive content on how the results of the new configurations are tested.
My question is: is it useful to also use Agentforce Vibe to test the new developments using a battery the Secenario-Based Tests so they can run automatically or should we still maintinain the classic manual/data import for testing?
Thanks
Forum Ambassador
Hello Alberto,
A lot of the hype around Agentforce Vibes is focused on building fast, not so much on testing properly. Right now, Vibes isn’t really designed to replace your traditional testing strategy. It’s great for quickly validating behavior, trying scenarios, and doing lightweight checks, but it’s not a full-blown automated testing framework where you define a structured suite of scenario-based tests that run consistently across environments.
So in practice, what most teams are doing is using Vibes for exploratory and rapid validation—basically simulating user interactions and seeing how the agent responds—while still relying on classic testing approaches for anything critical. That means manual QA, controlled data setups, and sometimes automated tests via Apex or external tools. If you try to rely only on Vibes, you’ll run into gaps like lack of repeatability, version control over test cases, and proper regression coverage.
Hope this helps!
