Known Gaps and Issues

This page contains known gaps and issues for Agentforce Vibes IDE

For a workaround and latest details, see this known issue in the Agentforce Vibes extensions GitHub repo.

When you create a new Agentforce Vibes IDE environment or return to one, you'll see a loading page and then the tooling activating once inside the IDE. Behind the scenes, the IDE is getting your environment ready and preloading and/or updating tooling for you. At some points while that's happening, you might not see any feedback on screen. When you first create an environment, you'll know everything's ready to go when you see "Welcome to Agentforce Vibes IDE".

When you authorize to an IP-restricted org from the IDE, you will get an error because the IP range for the IDE can vary. While you can add the IDE's outbound IP to your allow list, there are important caveats to consider: 1) it's not a static IP and will change in the future, so this isn't a one-time workaround and 2) that outbound IP could be used by any other environments. With those caveats in mind, if you want to find your IDE's current outbound IP, you can open the Terminal in the environment run curl https://ifconfig.me and your IP will be displayed. If the IP address changes, you will need to repeat these steps to adjust your IP allow list.

If you already have a DX project in a GitHub repo, you can clone the repo into your IDE. To clone a project using SSH, the IDE needs an SSH key that is recognized by GitHub, and the IDE cannot create one for you. To configure the IDE environment for SSH access, use the terminal in the IDE and follow the instructions on the GitHub website.

In the terminal in the IDE, clone your project from GitHub. Click the hamburger icon (the top icon in the Activity Bar) in the IDE, and use File > Open Folder to select the folder that was generated by the clone command.

When you import an existing GitHub project, the Agentforce Vibes IDE clones the project into the environment you create. If the project is in a private repository, the IDE can obtain a GitHub token on your behalf in order to access the repository. The IDE is able to do this because it is a trusted authentication application for GitHub, However, if your organization uses GitHub Enterprise, the on-premises version of GitHub, the IDE is not known to your GitHub server, and therefore cannot obtain a token on your behalf. To use GitHub Enterprise with the Agentforce Vibes IDE, create a new project from scratch using the empty template, just to get you into your new environment. When you reach your new environment, use the terminal to configure git credentials (https://git-scm.com/docs/gitcredentials) to your GitHub Enterprise server. Clone your project, and use the File menu to open your project folder in the IDE.

If you use the SFDX: Authorize an Org Command Palette option in the IDE, you got an OAUTH_APPROVAL_ERROR_GENERIC error. This error was first reported on July 26, 2024 and a fix was released to customers in Summer ’24 Patch 17 (250.17) on Aug 14, 2024.

This error affected all Agentforce Vibes IDE customers.

Workaround: Connect to your org from the IDE using the Salesforce CLI in the terminal of VS Code instead of through the Command Palette.

Execute this Salesforce CLI command in IDE's Terminal after you replace <ORG_ALIAS> with your choice of alias name.

sf org login device --alias <ORG_ALIAS> --set-default

Follow the "Action Required!" instructions from the CLI output by entering the listed code after you navigate to the verification URL. You may need to open the verification URL in an incognito window or in a different browser. If you're already logged into an org, the IDE authorizes that org. Otherwise, the IDE will prompt you to log into an org.

Issue: Users experience OAuth authentication failures when trying to authorize orgs in Agentforce Vibes IDE, encountering either OAUTH_APPROVAL_ERROR_GENERIC or invalid_grant: restricted IP errors.

Root Cause: Recent Salesforce policy changes now block uninstalled connected apps by default and enforce stricter IP restrictions through device activation requirements. Agentforce Vibes IDE uses dynamic public IPs that may not be included in users' configured IP ranges.

Symptoms:

• Browser displays OAUTH_APPROVAL_ERROR_GENERIC with URL parameters showing error=invalid_client&error_description=app+must+be+installed+into+org.
• OAuth flow fails with invalid_grant: restricted IP error.
• Users unable to complete org authorization in the Agentforce Vibes IDE.

Workarounds:

1. For the "app must be installed" error, follow the guidance in Prepare for Connected App Usage Restrictions Change
2. For IP restriction errors: Add Agentforce Vibes's IP ranges to your org's trusted IP ranges or profile-level login IP ranges (note that Agentforce Vibes IDE uses dynamic IPs, making this challenging)

Status: Engineering teams are working on adding the IDE connected app to Salesforce's trusted allowlist for internal connected apps, which should resolve the installation requirement. IP egress standardization is in the infrastructure backlog.

Related Issues:

CLI issue: GitHub Issue #3368

Salesforce Help: Device Activation Changes: Users experience OAuth authentication failures when trying to authorize orgs in the IDE, encountering either OAUTH_APPROVAL_ERROR_GENERIC or invalid_grant: restricted IP errors.