Contact Us 1-800-596-4880

Anypoint Code Builder (Beta) Release Notes

Open Beta Release: Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions, available from the IDE.

Cloud IDE for Anypoint Code Builder Desktop IDE for Anypoint Code Builder Web and Desktop IDE info

Use the Anypoint Code Builder integrated development environment (IDE) for your API designs, implementations, and integration development. Work locally with Anypoint Code Builder for Desktop on Microsoft Visual Studio Code (VS Code) or from your browser with Anypoint Code Builder on Anypoint Platform. The IDEs support the development lifecycle:

  • API specification design (OAS, RAML, or GraphQL), a mocking service for testing, source control, and publication to Anypoint Exchange

  • API implementation features for importing supported API specifications and autogenerating interfaces (scaffolding) for flows and error handlers within a Mule application

  • Integration development to connect systems, transform data to required formats, and provide business logic to manage messages and events programmatically within a Mule application


Application/Service IDE Version


Both IDEs


Visual Studio Code

Desktop IDE

1.76.1 (tested version)

Operating System

Desktop IDE

Mac OS Intel and ARM (M1 or M2), Windows 10 (tested version), Windows 11


Cloud IDE

v4.11.0 (built-in)

Mule runtime engine

Both IDEs

4.4.0-20230724 (built-in)


Both IDEs

2.4.0-20221212 (built-in)


Both IDEs

Adoptium Temurin (based on OpenJDK) jdk-11.0.19+7 (built-in)


Both IDEs

3.8.8 (built-in)

Browser Support

Both the web-based and desktop IDEs require authentication with Anypoint Platform.

CloudHub Environment

CloudHub deployments are to the Sandbox environment only.

Open Beta Releases

Anypoint Code Builder is currently in open beta.

Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions.

What’s New

Updates to the open beta introduce features and improvements:

September 2023 (Open Beta)

This update to the open beta introduces Anypoint Code Builder for Desktop on Windows and new features for desktop and cloud IDEs.

Known Issues

Limitation ID

Deployments to CloudHub 1.0 from within Anypoint Code Builder run on vCores allocated to the root organization only. You cannot deploy to a business group even if it has a sufficient vCore allocation. If your root organization lacks a sufficient vCore allocation, the error Failed to deploy to CloudHub: 400 occurs.

  • Workaround:
    Use Runtime Manager to deploy to the business group in the Sandbox environment in CloudHub, or increase the vCore allocation to the root organization in the Sandbox environment. To reallocate resources to your root organization, see Redistribute Resources Between Existing Business Groups. To manage environments, see Environments. For additional help, contact your organization administrator for Anypoint Platform.


When the desktop IDE launches for the first time, a corrupted dependency (.m2\repository\net\minidev\accessors-smart\1.2\accessors-smart-1.2.pom) can block the Anypoint Code Builder - Integration Extension when extracting the Mule runtime operation.

  • Workaround:
    Delete the dependency from .m2\repository\net\minidev\accessors-smart, and re-launch the IDE.


When launching the cloud IDE for the first time from Anypoint Code Builder, you must allow popups.


The link to the help page code-server Editing evolved dialogue does not work.


The list of trusted authors for a directory or file is not persistent across different browsers.


The UI does not provide a notification after you change the region in settings.json.


Selecting a project folder from the PROJECTS view in the Explorer causes Anypoint Code Builder to produce the error The file is not displayed in the text editor because it is a directory.


Adding a space at the end of an API specification name causes an error.

  • Workaround:
    Do not use spaces at the end of any project name.


In dark mode, error messages are difficult to read because of an issue with the color scheme in API Console.


API Console does not reflect changes immediately.


The RAML editor does not handle indentation correctly when you use tabs or spaces.


Anypoint Code Builder displays a Cannot read properties of undefined (reading 'name') error when failing to resolve a GraphQL type.


The Back button in the command palette does not work when running the MuleSoft: Import Asset from Exchange command.


The rescaffolding icon is not disabled after you rescaffold an API specification.


Moving the editors while searching for components from the UI canvas causes your search to be canceled.

  • Workaround:
    Avoid rearranging your editors when using the component palette in the canvas.


The canvas UI does not displays flows and components after scaffolding a Mule application.

  • Workaround:
    Wait for it to finish loading.


Using autocompletion to create a parameter for the value field in the XML adds an extra #[] statement.


Autocompletions and code suggestions do not follow the standard VSC/LSP pattern.


Autocompletion does not work properly when more than one connector has the same prefix.


Anypoint Connector for NetSuite (NetSuite Connector) does not have an icon in the component palette.


Anypoint Connector for Apache Kafka (Apache Kafka Connector) does not display the Test Connection option.


When you import a Mule project from Studio to Anypoint Code Builder, a DataWeave expression can produce syntax errors (identifiable by a red, wavy underline) in the configuration XML. The issue occurs because the IDE’s tooling is unable to automatically fetch the required dependencies from Mule runtime when the project loads.

  • Workaround:
    In the pom.xml file for the imported project, add this dependency as a child of the <dependencies/> element:



If you import a Mule project into Anypoint Code Builder that points to Anypoint Exchange (Exchange) version 3, authentication and dependency resolution errors occur because Anypoint Code Builder currently supports Anypoint Exchange version 2 only.

  • Workaround:
    In the pom.xml for the project, change the Exchange version from v3 to v2:

    1. Search for this element:

        <name>Anypoint Exchange</name>
    2. Change v3 to v2 in the id and url child elements:

        <name>Anypoint Exchange</name>


DataSense doesn’t identify functions provided by a connector.


DataSense doesn’t reflect array structures at the payload’s root level.


DataSense doesn’t work when a tag spans multiple lines.


DataWeave doesn’t recognize the larger context to which samples belong. So DataWeave requests sample data for all scripts within a single component.


DataWeave validations to produce Invalid input errors on some multiline scripts because Anypoint Code Builder does not decode Unicode characters for new lines in XML (&#10;). This limitation does not interrupt the correct execution of your Mule application.


Code highlighting breaks when you define a DataWeave multiline expression. This limitation does not interrupt the correct execution of your Mule application.


Anypoint Code Builder displays a popup message about opened ports when creating a Mule project.


Ending a second thread in a Scatter-Gather component before the first thread finishes freezes processing in Anypoint Code Builder.

  • Workaround:
    Manually select the other thread to continue processing.


Updates to metadata in one component don’t trigger metadata validation in subsequent components. This issue causes Anypoint Code Builder to display potential issues in the subsequent components.


The Mule configuration XML file sometimes fails to open immediately after you create a new Mule project.

  • Workaround:
    Open the file manually.


The Batch Job processor is not supported.


August 2023 (Open Beta)

This update to the open beta introduces Anypoint Code Builder for Desktop on MacOS and a new feature for desktop and cloud IDEs.

  • Anypoint Extension Pack on Visual Studio Marketplace to support API specification design (OAS 3 and RAML), API implementation, and integration development

    Install the pre-release_version. Attempting to install the _release version produces an error.

  • Support for the Mac operating system running on Intel or ARM (M1 or M2) processors (see Compatibility)

  • Desktop and cloud IDE support for the following features:

June 2023 (Open Beta)

The update to the open beta for the web-based IDE introduces these features and improvements:

  • Support for EU Cloud: EU Cloud users of Anypoint Platform can now use Anypoint Code Builder from their management plane.

    See Access Code Builder From EU Cloud for more information.

  • Synchronization between a local API specification and Mule project: You can now work on your API specification and its Mule project implementation simultaneously.

    Anypoint Code Builder enables you to scaffold your API specification into a Mule project without publishing it to Exchange. You can work on your Mule project, then edit the API specification, and re-scaffold it to reflect your new changes. Both API design and API implementation tasks are now synchronized. You can then publish your API specification and deploy your Mule project from there.

  • Updated UI canvas and code snippet support:

    • Directly import connectors from the canvas instead of using the dedicated command.

    • Use code snippets. See Work with Code Snippets for more information.

April 24, 2023 (Open Beta)

The update to the open beta for the cloud IDE introduces a number of features and improvements:

  • Anypoint Code Builder migrated to a new underlying architecture.

  • The URL for your cloud IDE instance changed. You can get the new URL by launching the cloud IDE from the central page or checking the IDE details.

  • Your session cookie changed, so you must update it when pinging a locally deployed application from a REST client.

April 2023 (Open Beta)

The update to the open beta for the cloud IDE introduces these features and improvements:

  • Business group support enables you to control access to resources when working with assets from Anypoint Exchange. See Working With Business Groups.

  • Search filters enable you to refine your search results when looking for an API asset from Anypoint Exchange. See Filter Search Results for more information.

  • The canvas UI enables you to add components to flows in your integration.