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

Salesforce Code Builder で再現し、Agentforce Vibes のアクティベーションログを sf org display --json および sf org list --json と比較する。auth.connectionResolved と Platform MCP env resolved のエントリを追跡し、認証済み org ID によって空のインスタンス URL が生成される理由を特定する。正しい Salesforce ホストが解決され、Vibes が正常に開けば完了とする。

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.