Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Agentforce Vibes fails to open in Code Builder despite successful org authentication

Open
  • Is something wrong?
#280 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
node.js
Domain
cloud, developer-experience, tooling

Research direction

Reproduce in Salesforce Code Builder and compare the Agentforce Vibes activation logs with sf org display --json and sf org list --json. Trace the auth.connectionResolved and Platform MCP env resolved entries to determine why the authenticated org ID produces an empty instance URL; done means the correct Salesforce host is resolved and Vibes opens normally.

Written by the indexing model from the issue text.

Description

Agentforce Vibes IDE does not open/function in Salesforce Code Builder. The Salesforce CLI connection to the org is healthy, and the Agentforce Vibes extension and its MCP services all initialize successfully, but the Vibes runtime appears to resolve the Salesforce instance URL incorrectly.

Environment:

Salesforce Code Builder
Agentforce Vibes IDE extension: 4.15.0
Code-server: 1.112.0
Salesforce CLI: 2.143.6
Node.js: v22.23.1
Org: Developer Edition / OrgFarm

Org authentication is working correctly. sf org display --json and sf org list --json both report:

Connected Status: Connected
Org ID: 00DNS00000vyXDB2A2
Instance URL: https://orgfarm-c5ddce12f9-dev-ed.trailblaze.my.salesforce.com/
API Version: 67.0
Default org: true

The user has the following relevant permission sets assigned:

Code Builder Package
Code Builder User
Agentforce Developer and Admin Tools
TrailheadAgentforceDeveloper

The Agentforce Vibes activation log shows that the extension itself initializes successfully:

extension.activated ... version=4.15.0

The MCP services also start successfully:

serverName="Salesforce DX" transport=stdio
serverName="Salesforce API Context" transport=streamable-http
serverName="Salesforce Metadata Experts" transport=streamable-http

The Vibes skills package also installs successfully:

@salesforce/afv-skills resolvedVersion=1.35.0

However, the Vibes runtime subsequently reports:

auth.connectionResolved
orgId=00DNS00000vyXDB2A2
username=

and then:

Platform MCP env resolved: instanceUrl=https:/// env=prod

It consequently constructs MCP/AI endpoints with an empty Salesforce host, for example:

gatewayBaseUrl=https:///ai/gpt/v1

The Salesforce CLI independently resolves the same authenticated org to the correct instance URL, so this does not appear to be a general Salesforce CLI authentication problem.

The main question is why Agentforce Vibes in Code Builder is receiving the org ID but resolving the Salesforce instance URL as https:///, preventing Vibes from opening/working normally.

Dominant language
No language data
Stars
35
Forks
2
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forcedotcom/code-builder-feedback

All issues in forcedotcom/code-builder-feedback

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.