Troubleshooting AI Features in Anypoint Code Builder

The following errors sometimes occur when you use MuleSoft Vibes in Anypoint Code Builder.

Unexpected Results When Using Mulesoft Vibes

If the generated flow doesn’t return accurate or useful results for your message, try rewriting your message and follow the guidelines to write an effective message.

If results are still inconsistent, verify that your project context and Mulesoft Vibes settings are correctly configured.

Troubleshoot Mulesoft Vibes Access Errors

If you can’t open MuleSoft Vibes, verify the following:

You are logged in to Anypoint Platform from the IDE. For more information, see Log in to Anypoint Platform from the IDE.
You have the required Anypoint Code Builder permissions, including:
- Mule Developer Generative AI User
You have the required permissions for the tools in the MuleSoft MCP Server that MuleSoft Vibes uses to generate accurate responses.

Required Permissions for MuleSoft Vibes

MuleSoft Vibes always uses the permissions of the logged-in Anypoint Platform user. MuleSoft Vibes can’t perform any action that the user doesn’t already have permission to perform.

Here are the permissions required across capabilities in the MuleSoft MCP Server:

Required Permissions

Anypoint Monitoring * Monitoring Viewer

API Manager * Manage APIs Configuration * Manage Policies * View APIs Configuration * View Policies

Exchange * Exchange Administrator * Exchange Contributor * Exchange Creator * Exchange Viewer

General * View Organization * View Connected Applications

Runtime Manager * Read Applications * Create Applications * Read Runtime Fabrics * CloudHub Network Viewer

Usage * Usage Viewer

If you want to configure MuleSoft Vibes with a different set of permissions, you must:

Remove or disable the out-of-the-box MuleSoft MCP Server.
Follow the steps in the MuleSoft MCP Server documentation to set up a connected app with the desired permissions.

Troubleshoot Anypoint Platform Authorization Errors

If you receive an authorization error, contact your Anypoint Platform organization administrator. If you are the organization administrator, check the following:

The user has the required Anypoint Code Builder permissions.
Your Anypoint Platform organization is current and active.

Vibes Features are Unresponsive or Fail to Load

If MuleSoft Vibes features aren’t working as expected, verify that your system points to the JDK used by Anypoint Code Builder.

Configure JAVA_HOME on macOS

Identify the path where Anypoint Code Builder has installed the JDK. It typically follows this pattern:

/Users/<your_username>/AnypointCodeBuilder/java/<jdk_version>/Contents/Home
Open your shell profile (usually ~/.zshrc for Zsh or ~/.bash_profile for Bash) in a text editor:
```
nano ~/.zshrc
```
Add these lines, replacing <path_to_jdk> with the path identified in the previous step:
```
export JAVA_HOME="<path_to_jdk>"
export PATH="$JAVA_HOME/bin:$PATH"
```
Save the file and reload the profile:
```
source ~/.zshrc
```
Verify the configuration by running echo $JAVA_HOME and java -version.

Configure JAVA_HOME on Windows

Identify the path where Anypoint Code Builder has installed the JDK. It typically follows this pattern:

C:\Users\<your_username>\AnypointCodeBuilder\java\<jdk_version>
Open Windows Search, enter Edit the system environment variables, and then select Environment Variables.
In User variables or System variables, create or update JAVA_HOME with your JDK path.
Update the Path variable and add this line:

%JAVA_HOME%\bin
Open a new Command Prompt and verify the configuration:
```
echo %JAVA_HOME%
java -version
```