Anypoint Code Builder Release Notes | MuleSoft Documentation
# Anypoint Code Builder Release Notes
Cloud IDE 
Desktop IDE 
**Open Beta Release** : The **cloud IDE is in open beta**. Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions, available from the IDE.
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, and AsyncAPI), a mocking service for testing, source control, and publication to Anypoint Exchange
  * API implementation features for importing supported API specifications (OAS, RAML, GraphQL, and AsyncAPI) 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


## July 21, 2025
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE.
  * Extension pack version: 1.9.2
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.9.2
This cloud IDE version runs the 1.9.2 extension pack.


For extension versions, see Change Log in the Visual Studio Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
  * Support for Mule runtime engine version 4.9.7 LTS with Java version 17. See Compatibility.


## July 4, 2025
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE.
  * Extension pack version: 1.9.0
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.9.0
This cloud IDE version runs the 1.9.0 extension pack.


For extension versions, see Change Log in the Visual Studio Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
This release introduces these features:
  * Map Fields in DataWeave Expressions with AI
  * Generate DataWeave Transformations with AI
  * Design API Specs with AI
  * Use A2A Connector (Beta) with Anypoint Code Builder
  * Use MCP Connector 1.0 (Generally Available) with Anypoint Code Builder
  * Create MUnit Test from Flow
  * Scope MUnit Tests to Specific Processors from UI
  * Comment Out Components in Canvas
  * Navigate to Flows from Connectors
  * Review Scaffolding Errors in Output Panel
  * Open Projects in Canvas by Default
  * Enter Properties as Values in Fields in UI
  * Check Java and Mule Runtime Compatibility for All Connectors in Your Project
  * Use Anypoint Code Builder with Windows 11
  * Agentforce Command Removed
  * 

### Map Fields in DataWeave Expressions with AI
Automatically generate field-to-field mappings based on input and output metadata with the assistance of AI.
For more information, see Map with AI.
### Generate DataWeave Transformations with AI
Generate full DataWeave transformations from input and output sample data with the assistance of AI.
For more information, see Map and Transform with AI.
### Design API Specs with AI
Use Einstein generative AI to generate API specs from a conversation.
For more information, see Designing API Specs with AI.
### Use A2A Connector (Beta) with Anypoint Code Builder
This release introduces support for Anypoint Connector for Agent2Agent (A2A Connector) (beta). A2A Connector (beta) facilitates inter-agent communication for Large Language Model (LLM) agents and other applications by implementing the A2A protocol. This enables agents to interact and delegate specialized tasks to other agents. See Creating Integrations Using Agentforce and Built-In Connectors.
_A2A Connector is a beta connector that is subject to the Beta Services Terms atAgreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and the Non-GA Gen AI and Non-GA Credit Consumption terms in the Product Terms Directory. Use of this beta connector with external systems or services consumes Mule messages and is at the Customer’s sole discretion._
### Use MCP Connector 1.0 (Generally Available) with Anypoint Code Builder
This release introduces support for the generally available version of Anypoint Connector for MCP (MCP Connector). Previously, Anypoint Code Builder supported the beta version of MCP Connector. If you used the beta version of MCP Connector, remove `-Dmule.http.service.implementation=NETTY` from Runtime: Default Arguments in MuleSoft Settings. Also, the Design Service: System Properties setting is removed from MuleSoft Settings.
MCP Connector helps you expose your Mule application as a tool that any AI client supporting Model Context Protocol (MCP) can use to perform real-world actions. See Creating Integrations Using Agentforce and Built-In Connectors.
### Create MUnit Test from Flow
Create MUnit tests for your Mule project directly from the context menu of a flow.
For more information, see Create a Test from a Flow.
### Scope MUnit Tests to Specific Processors from UI
Select the processors and attributes in a Mule flow from the UI for testing to i​ncrease precision, identify issues faster, and create tests more efficiently.
For more information, see Targeting Specific Processors and Attributes in Your Test.
### Comment Out Components in Canvas
Comment out components directly in Anypoint Code Builder canvas. Disabled components can also be deleted in bulk for cleanup purposes.
### Navigate to Flows from Connectors
You can now open the target flow referenced by a connector, using the **Go to Flow** option in the context menu for application flows and MUnit test flows to trace and manage application logic across modular flows.
### Review Scaffolding Errors in Output Panel
Now it’s even easier to troubleshoot errors when creating a project. In the Output panel, there’s a new **MuleDX Server - Scaffolding** option. Select that option to show the MuleDX Server log content that’s related to scaffolding only.
For more information, see Opening the Output Panel.
### Open Projects in Canvas by Default
Anypoint Code Builder now opens projects in the canvas by default. You can save and debug your applications directly from the UI without switching views, streamlining your low-code experience.
### Enter Properties as Values in Fields in UI
Property mode `{}` now makes it possible to enter properties in number and boolean fields in the UI. Previously, it was possible only in the code editor.
### Check Java and Mule Runtime Compatibility for All Connectors in Your Project
Verify that your local and Anypoint Exchange connectors are compatible with your Java and Mule runtime version for your projects. Project Properties now tells you about incompatible versions and lets you fix them right away, accelerating development and reducing blockers, especially when importing projects. Previously, Project Properties verified compatibility of Anypoint Exchange connectors only.
For more information, see Version Settings for Mule, Java, and Connectors.
### Use Anypoint Code Builder with Windows 11
Anypoint Code Builder Desktop IDE now supports Windows 11.
For more information, see Compatibility.
### Agentforce Command Removed
The **MuleSoft: Open Agentforce** command is removed from the Command Palette. You can use the toolbar button to access the Agentforce panel when available.
## Fixed Issues
Issue Resolution | ID  
---|---  
When you define a DataWeave multiline expression, code highlighting now works as expected.  
## May 27, 2025
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE.
  * Extension pack version: 1.8.2
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.8.3
This cloud IDE version runs the 1.8.2 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
  * Authentication support for Cursor, Trae, and Windsurf.
  * Support for Mule runtime engine version 4.9.4 LTS with Java version 17. See Compatibility.


## April 29, 2025
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE.
  * Extension pack version: 1.8.1
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.8.3
This cloud IDE version runs the 1.8.1 extension pack.
For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
  * Authentication support for Cursor, Trae, and Windsurf.
  * Support for Mule runtime engine version 4.9.4 LTS with Java version 17. See Compatibility.


## April 29, 2025
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE.
  * Extension pack version: 1.8.1
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.8.3
This cloud IDE version runs the 1.8.1 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
This release introduces support for Anypoint Connector for MCP (MCP Connector) (beta). MCP Connector (beta) helps you expose your Mule application as a tool that any AI client supporting Model Context Protocol (MCP) can use to perform real-world actions. For example, your MCP client can trigger a process, look up data, or transform records. See Creating Integrations Using Agentforce and Built-In Connectors.
_MCP Connector is a beta connector that is subject to the Beta Services Terms atAgreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and the Non-GA Gen AI and Non-GA Credit Consumption terms in the Product Terms Directory. Use of this beta connector with external systems or services consumes Mule messages and is at the Customer’s sole discretion._
## March 21, 2025
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE.
  * Extension pack version: 1.8.0
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.8.0
This cloud IDE version runs the 1.8.0 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
This release introduces these features:
  * New DataWeave Transformation Builder Tool.
Transform your message payload, attributes, and variables to the required output format and data structure with DataWeave Transformation Builder. See Open Transformation Builder.
  * Refine your flows through natural language interactions.
Anypoint Code Builder dynamically updates your flow code based on your latest instructions, ensuring an easy and efficient workflow. Plus, access your chat history to track changes. See Developing Integrations Using Agentforce.
  * Validate and publish your API project to Anypoint Exchange through a new intuitive user interface.
See Publishing API Projects to Exchange.
  * Build Agentforce integrations using Agentforce Connector 1.0.1 and Einstein AI Connector 1.1.1.
See Creating Integrations Using Agentforce and Built-In Connectors.
  * Agentforce for Anypoint Code Builder Generative Flows is now available on these Anypoint Platform instances on Hyperforce: Canada Cloud and Japan Cloud.
  * New documentation to help you migrate your Anypoint Studio Mule projects to Anypoint Code Builder.
Learn how to import your Mule projects into Anypoint Code Builder to unlock a modern development experience with faster startup times, streamlined collaboration, and the integration of MuleSoft for Agentforce: Topic Center to enable API projects for topics and agents. See Migrate Your Mule Project from Anypoint Studio to Anypoint Code Builder.
  * The Einstein generative flow feature is now called the Agentforce generative flow feature.


### Fixed Issues
Issue Resolution | ID  
---|---  
DataSense now works as expected when a tag spans multiple lines.  
DataSense now works as expected when you create a project with Mule runtime version 4.4 and no other runtime versions are downloaded.  
## February 6, 2025
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the Cloud IDE.
  * Extension pack version: 1.7.0
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.7.1
This cloud IDE version runs the 1.7.0 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
This release introduces these features:
  * Support for MuleSoft for Agentforce: Topic Center.
    * Use the visual editor when you design an API to enable your API specifications for topics and agents.
    * Make your topic and action-enabled APIs available in Salesforce using Salesforce API Catalog.
    * Augment agent functionality by assigning topics to Agentforce agents in Agent Builder.
    * Use the provided governance rules to validate that your API is ready to generate agent actions and topics in Salesforce.
  * Run MUnit tests from the canvas. See Testing Projects with MUnit.
  * Configure proxy settings. See Using a Proxy in Anypoint Code Builder.
  * Streamline productivity with performance enhancements for DataSense, flow canvas rendering, and connector configuration testing.
  * Support for Mule runtime engine version 4.9 LTS with Java version 17. See Compatibility.


### Fixed Issues
Issue Resolution | ID  
---|---  
A notification now appears after you change the region in the `settings.json` file.  
XML formatting is no longer corrupted when you add or update a connection configuration, or when you use the **Format Document** menu option.  
Avro suggestions now appear when you define an Avro schema and declare a record inside a record property.  
Correct suggestions now display for inline Avro schema payloads. The issue occurred inside maps that contained arrays.  
Correct suggestions now display for values in fields of type map.  
Syntax errors in DataWeave expressions in projects imported from Studio no longer occur. Anypoint Code Builder now automatically fetches the required dependencies when the project loads.  
When you use a proxy, the Mule runtime options now appear in the UI form for creating a new integration project. You can click **Create Project** to create the project.  
## December 9, 2024
Anypoint Code Builder releases a new feature in the Anypoint Extension Pack.
  * Extension pack version: 1.6.0
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
  * This product is now available on Hyperforce.
Anypoint Platform instances on the Hyperforce infrastructure are:
    *     * Exceptions:
      * Einstein for Anypoint Code Builder Generative Flows is available only on US and EU cloud hosts. Canada and Japan cloud hosts are currently not supported.
      * Cloud IDE is available only on US and EU cloud hosts. Canada and Japan cloud hosts are currently not supported.
  * “Design Center” UI labels are renamed to “MuleSoft VCS”.


### Fixed Issues
Issue Resolution | ID  
---|---  
Anypoint Connector for Zoom (Zoom Connector) component configuration view now correctly displays relevant options.  
Adding a transform connector no longer incorrectly inserts `#[]` in script fields. Previous: `<![CDATA[#["test"]]]>` New: `<![CDATA["test"]]>`  
## November 4, 2024
Anypoint Code Builder releases a new feature in the Anypoint Extension Pack and the cloud IDE.
  * Extension pack version: 1.5.0
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.5.0
This cloud IDE version runs the 1.5.0 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
The release introduces the following feature:
  * The Einstein for Anypoint Code Builder Generative Flows feature is now enabled and managed in Anypoint Platform Access Management.
For more information, see Enabling Einstein for Anypoint Platform.


### Fixed Issues
Issue Resolution | ID  
---|---  
JMS Connector connections can now be validated with the **Test Connection** button.  
## October 8, 2024
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the cloud IDE.
  * Extension pack version: 1.4.1
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.4.6
This cloud IDE version runs the 1.4.1 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
This release introduces these features:
  * Advanced Data Types
  * Connection Configurations from the UI
  * Code Coverage Reports
  * Deploy to CloudHub 2.0
  * Publish Mule Projects to Anypoint Exchange
  * AsyncAPI Specification Design and Governance
  * AsyncAPI Support for Avro Schema Fragments
  * AsyncAPI Implementation Support for Solace PubSub+ and Salesforce Platform Events Connectors
  * Support for Mule Version 4.8
  * Enhanced API Auto-Completion
  * API Autodiscovery
  * Enhanced Debugging
  * Custom Connector Support
### Fixed Issues
Issue Resolution | ID  
---|---  
JMS Connector connections can now be validated with the **Test Connection** button.  
## October 8, 2024
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the cloud IDE.
  * Extension pack version: 1.4.1
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.4.6
This cloud IDE version runs the 1.4.1 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
This release introduces these features:
  * Advanced Data Types
  * Connection Configurations from the UI
  * Code Coverage Reports
  * Deploy to CloudHub 2.0
  * Publish Mule Projects to Anypoint Exchange
  * AsyncAPI Specification Design and Governance
  * AsyncAPI Support for Avro Schema Fragments
  * AsyncAPI Implementation Support for Solace PubSub+ and Salesforce Platform Events Connectors
  * Support for Mule Version 4.8
  * Enhanced API Auto-Completion
  * API Autodiscovery
  * Enhanced Debugging
  * Custom Connector Support


#### Advanced Data Types
The connection configuration panel in the canvas UI adds support for configuring connections, objects, arrays of non-primitive types, and multi-level dynamic lists. In the previous release, the configuration panel supported unions, arrays of primitive types, file selectors, and password fields.
For more information, see Adding a Component to Your Project.
#### Connection Configurations from the UI
Connection configurations are global configurations that more than one component in a project can use. Anypoint Code Builder improves workflow by enabling you to check for components that use the connection through the UI.
For more information, see Adding a Component to Your Project.
#### Code Coverage Reports
Anypoint Code Builder adds code coverage reports for testing integration and implementation projects with MUnit.
For more information, see Running MUnit Tests with Coverage.
Additionally, you can now run MUnit tests in Anypoint Code Builder without setting your credentials in Maven.
#### Deploy to CloudHub 2.0
In addition to supporting deployments of your integrations to CloudHub, Anypoint Code Builder adds support for deployments to CloudHub 2.0.
For more information, see Deploying Mule Apps to CloudHub and CloudHub 2.0.
#### Publish Mule Projects to Anypoint Exchange
Anypoint Code Builder adds functionality for publishing project templates and project examples to Anypoint Exchange. Publishing to Exchange enables your team to reuse your applications.
For more information, see Publishing a Mule Project to Exchange.
#### AsyncAPI Specification Design and Governance
Anypoint Code Builder now supports creating, designing, and governing AsyncAPI 2.6 specifications.
For more information, see:
  * Creating and Importing AsyncAPI API Specifications
  * Validating API Specifications Against Governance Rulesets


#### AsyncAPI Support for Avro Schema Fragments
Anypoint Code Builder adds support for creating and designing Apache Avro schema fragments. Ensure data consistency and interoperability in distributed systems by defining Avro schemas with structured data, including data types and fields.
For more information, see Creating and Using API Spec Fragments
#### AsyncAPI Implementation Support for Solace PubSub+ and Salesforce Platform Events Connectors
Anypoint Code Builder adds support for Solace PubSub+ and Salesforce platform events connectors.
Expand your integration capabilities and streamline event-driven architectures. For more information, see Supported Message Brokers.
Implementing AsyncAPI specifications using DataSense for Avro schemas requires Mule 4.8 or later.
#### Support for Mule Version 4.8
Anypoint Code Builder adds support for Mule version 4.8 with Java versions 11 and 17. For more information, see Mule and Java version support.
#### Enhanced API Auto-Completion
Anypoint Code Builder introduces enhanced API auto-completion. Instead of typing Ctrl+Space to activate the auto-completion menu in your API spec, you can place your cursor at the location in your API spec file where you require suggestions. If the line has some content, press Tab, press Space, or start typing after the content on the line to launch the menu. To close the auto-completion menu, press Escape.
  * Mule > Editor > Auto-completion: Enablement
This setting is disabled by default.
  * Mule > Editor > Auto-completion: Trigger Delay


For more information on using auto-complete, see Use Auto-Complete in the Editors.
#### API Autodiscovery
Anypoint Code Builder supports configuring Mule apps for tracking requests with Autodiscovery.
Configure a Mule app to send request data to an API running on a Mule Gateway runtime in API Manager. The API tracks this data in charts in API Manager.
For more information, see Tracking Requests with Autodiscovery.
#### Enhanced Debugging
Anypoint Code Builder adds breakpoint indicators in the canvas UI for components that have one or more breakpoints in the configuration XML. Indicators also display when stepping through a flow while debugging.
Additionally, you can add and remove breakpoints on components in the canvas UI.
For more information, see Debugging Mule Applications.
#### Custom Connector Support
Anypoint Code Builder now supports custom connectors that are locally bundled or published to Exchange.
For locally bundled connectors, add the dependency to your integration project by referencing the Maven dependency in your `pom.xml` file.
For connectors published to Exchange, add the component from the **Add Component** panel using the **Search in Exchange** toggle.
### Fixed Issues
Issue Resolution | ID  
---|---  
The **Governance Rulesets** and **Governance Results** panels now update as expected when more than one project folder is open in a VS Code workspace.  
After iteratively scaffolding an API spec into an implementation project, the **Data** and **Functions** tabs in the expression builder no longer display the "loading" animation.  
## August 17, 2024
Anypoint Code Builder releases a new feature in the Anypoint Extension Pack and the cloud IDE.
  * Extension pack version: 1.3.0
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.3.0
This cloud IDE version runs the 1.3.0 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
### What’s New
The release introduces the following feature:
  * You can now use the Einstein for Anypoint Code Builder Generative Flows feature to jumpstart your integration development by generating flows for you. For more information about this feature, see Developing Integrations Using Agentforce.


### Fixed Issues
Issue Resolution | ID  
---|---  
The **Governance Rulesets** and **Governance Results** now update as expected when more than one folder is open in a VS Code workspace.  
The **Preview** tab in the expression builder UI no longer produces an `Internal Error` message when you configure an attribute of a component’s child element in the XML editor _and_ that attribute accepts DataWeave expressions. This issue affected all components with child attributes that accept expressions. The following example displays a child element with an attribute that contains a DataWeave expression:  
## July 2, 2024
This patch release addresses Anypoint Code Builder issues.
### Fixed Issues
Issue Resolution | ID  
---|---  
You no longer have to update the runtime version when deploying a Mule application with Mule runtime version 4.6 or 4.7. This issue occurred when deploying to CloudHub from the IDE.  
A tooling client error no longer appears after creating a Java class, adding a New operation from the Java Module to a flow, selecting the class, and then refreshing Constructor.  
The XML now reflects changes after configuring the Send operation of Anypoint Connector for Email (Email Connector) from the component configuration panel.  
After changing the class setting in the **Class** field, you no longer have to refresh the **Method** field before selecting from the list of methods in the class. This issue occurred when updating the Invoke, Invoke Static, or New operations from the Java Module in the configuration panel.  
To import DataWeave libraries when using functions outside of the Core library, you no longer have to use the **Quick Fix** option. The DataWeave libraries are now imported automatically.  
The feedback button for the open beta of AsyncAPI support to implement event-driven architecture now consistently appears in the canvas.  
Patching the desktop IDE extensions requires a manual update or installation of the Anypoint Extension Pack. The cloud IDE is updated automatically.
  * Extension pack version: 1.2.2
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.2.4
This cloud IDE version runs the 1.2.2 extension pack.
For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
## June 24, 2024
AsyncAPI Beta: AsyncAPI 2.6 and 2.0 implementation features are now available for use in Anypoint Code Builder. The minimum Mule runtime engine requirement for this feature is Mule 4.6.
Before you can use these features, your Anypoint Platform organization administrator must accept the Beta terms and conditions from the Anypoint Code Builder landing page in Anypoint Platform. For guidance, see Implementing AsyncAPI Specifications.
Anypoint Extension Pack has not changed since the June 4, 2024 release. If you installed or upgraded your extensions on the desktop IDE in that release, no installation or upgrade is required. The cloud IDE was updated automatically in that release.
To learn about the AsyncAPI journey, see AsyncAPI Support to Implement Event-Driven Architecture.
For more information, see Known Issues and Compatibility.
## June 4, 2024
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the cloud IDE.
  * Extension pack version: 1.2.1
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.2.1
This cloud IDE version runs the 1.2.1 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
### What’s New
The release introduces the following features:
  * DataWeave Expression Builder
  * Component Configuration Enhancements
  * Support for Multiple Mule Runtime Versions with Java 17 or 11
  * Custom Java Classes and Code
  * Maven Settings
  * MUnit Support
  * API Governance for REST APIs


For more information, see Known Issues and Compatibility.
#### DataWeave Expression Builder
Use the DataWeave expression builder when configuring your integrations and implementations from the UI.
DataWeave is a programming language designed for transforming data. Most components in Mule application flows use DataWeave expressions to select and transform messages (payload and attributes) or Mule variables.
The DataWeave expression builder helps you configure fields of components that accept expressions (**fx** fields). For each expression field, the feature provides an extra panel with the following tabs:
  * **Data** for selecting a value (payload, attributes, or a Mule variables)
  * **Functions** for selecting DataWeave functions to use in your expressions
Function documentation is available from this tab by mousing over a function and getting details, including parameter descriptions and examples.
  * **Preview** for running the expression on sample data


In addition, you can use autocomplete from an expression (**fx**) field for a component to select DataWeave functions from the Core module and other values accepted in this field.
For details, see Using DataWeave Expressions and Transformations in Anypoint Code Builder.
For more information about DataWeave and the Mule event structure, see DataWeave Overview and Mule Events.
#### Component Configuration Enhancements
Configure more of your integrations and implementations from the canvas UI. The configuration panel for components adds:
  * An **Input/Output** tab to existing tabs (**General** , **Advanced** , and **Notes**) for Mule event metadata from the payload, attributes, Mule variables
  * Support for additional data types in the configuration fields:
    * File selectors
    * Passwords
    * Array (primitive types only)
    * Union for some configurable data sets


For examples, see Using DataWeave Expressions and Transformations in Anypoint Code Builder.
#### Support for Multiple Mule Runtime Versions with Java 17 or 11
Anypoint Code Builder now supports Mule runtime versions 4.4, 4.6, and 4.7 and compatible Java versions (Java 11 or Java 17) to run Mule apps for your implementation and integration projects (see supported Mule and Java versions). In addition, when you create an integration project from a template or example project in Anypoint Exchange, the asset search displays assets set to use Mule 4.4 or higher, instead of 4.4 only.
Select the versions to run when creating or importing Mule applications in Anypoint Code Builder and when scaffolding an API specification into an implementation project.
The following settings are new in this release:
  * **Mule > Application: Default Mule Runtime And Java Versions**: Sets default Mule and Java versions for all projects.
  * **Project Properties** tabs for setting and changing Mule runtime, Java, and connector versions in an implementation or integration project.
This feature is useful for updating to the latest minor version or when importing projects that use unsupported versions.
  * **Mule: Home Directory** : Set the home directory for Mule runtime and Java downloads.
This setting replaces the runtime settings **Mule > Runtime: Mule Home** and **Mule > Runtime: Mule Runtimes Directory**, which are no longer present in the **Settings** tab. In addition, the IDE no longer uses the directory `${user.home}/muleRuntimes/` to store Mule runtime versions.


Anypoint Code Builder - Mule Runtime Extension (`salesforce.mule-dx-mule-runtime`) is removed from Anypoint Extension Pack in this release. Instead of supplying a bundled runtime, the IDE provides an interface for downloading and installing runtime versions to use in your projects.
To remove the runtime extension from VS Code, open the **Extensions** panel, click **Anypoint Code Builder - Mule Runtime Extension** , and select **Uninstall**.
See Version Settings for Mule, Java, and Connectors for project and default version settings.
#### Custom Java Classes and Code
The Java module is now bundled into Anypoint Code Builder.
When you create a new Java class in a project, Anypoint Code Builder automatically adds the necessary dependencies to the project’s `pom.xml` and the namespace and schema locations to the configuration XML for the project.
New integration and implementation projects now add the directories `src/main/java` and `/src/test/java` for your custom Java work.
For documentation, see Configure the Java Module Using Anypoint Code Builder.
To use auto-complete from the application XML to find module configuration options and to display lists of available Java classes and methods in a selected class, install Extension Pack for Java from Microsoft to the IDE.
#### Maven Settings
To avoid changing any of your preferred Maven settings in `settings.xml`, Anypoint Code Builder now creates a separate settings file, `acb_settings.xml`.
The setting **Mule: Home Directory** , in the **Settings** tab, configures the location of this file. By default, the full path to the file is `{user.home}/AnypointCodeBuilder/maven/acb_settings.xml`.
For details, see Maven Settings Files in Anypoint Code Builder.
#### MUnit Support
Anypoint Code Builder introduces limited support for testing with MUnit.
Run, modify, and create MUnit tests for your implementation and integration projects in Anypoint Code Builder. Import projects that contain MUnit test files. Test configuration is supported through the XML editor only at this time. For more information, see Testing Projects with MUnit.
Some MUnit features supported by Anypoint Studio are not supported by Anypoint Code Builder in this release.
#### API Governance for REST APIs
Anypoint Code Builder now supports API Governance for REST APIs:
  * Check conformance status of a project.
  * Add rulesets to your project.
You can also remove rulesets, change ruleset versions, and review ruleset configurations.
  * Run and re-run validations against your API specifications.
For supported specifications, see Compatibility.
  * Monitor the progress of a validation.
  * Fix conformance issues.


See Validating API Specifications Against Governance Rulesets.
## April 19, 2024
Anypoint Code Builder updates the built-in Mule runtime engine to patch version `4.4.0-20240408`.
The Mule version is updated automatically in the cloud IDE but requires a manual update or installation of the Anypoint Extension Pack in the desktop IDE.
  * Extension pack version: 1.0.8
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.1.4
This cloud IDE version runs the 1.0.8 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
## February 14, 2024
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the cloud IDE.
  * Extension pack version: 1.0.7
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.1.3
This cloud IDE version runs the 1.0.7 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
### What’s New
The release introduces the following features:
  * Component Configuration Panel in the UI
  * Integration Project Creation from Templates and Examples
  * API Design Project Improvements
  * Configuration XML File Creation Enhancement
See Validating API Specifications Against Governance Rulesets.
## April 19, 2024
Anypoint Code Builder updates the built-in Mule runtime engine to patch version `4.4.0-20240408`.
The Mule version is updated automatically in the cloud IDE but requires a manual update or installation of the Anypoint Extension Pack in the desktop IDE.
  * Extension pack version: 1.0.8
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.1.4
This cloud IDE version runs the 1.0.8 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
For more information, see Known Issues and Compatibility.
## February 14, 2024
Anypoint Code Builder releases new features in the Anypoint Extension Pack and the cloud IDE.
  * Extension pack version: 1.0.7
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.1.3
This cloud IDE version runs the 1.0.7 extension pack.


For extension versions, see Change Log in the VS Code Marketplace.
### What’s New
The release introduces the following features:
  * Component Configuration Panel in the UI
  * Integration Project Creation from Templates and Examples
  * API Design Project Improvements
  * Configuration XML File Creation Enhancement


#### Component Configuration Panel in the UI
Anypoint Code Builder introduces a configuration panel in the UI for components, such as connector operations, within integration and implementation projects. This feature simplifies component configuration.
The component configuration panel provides configuration options that are also available through the configuration XML files for your projects. Some components and fields continue to require configuration through the XML in this release. Continue to use XML for complex fields, identified as read-only fields in the UI, and for global configurations, such as connection configurations.
You can open the configuration panel from the canvas or from a configuration XML file within your project. See Add a Component to Your Project and Open a Component in the Canvas from the XML Editors.
#### Integration Project Creation from Templates and Examples
Anypoint Code Builder adds the ability to import a template or example from Anypoint Exchange into an integration project within Anypoint Code Builder. After importing, you can continue to develop your integration. For information about templates and examples in Exchange, see Asset Types.
For guidance with importing from Exchange, click the tab **Start with a Project Template or Example** in the procedure Create an Integration Project.
#### API Design Project Improvements
This release introduces improvements and simplifications to the design process:
  * Import API design projects from Design Center into Anypoint Code Builder. For details, see Import an API Specification from Design Center.
  * Publish your API specifications and fragments to Anypoint Exchange without first syncing your code changes with the Anypoint source control management (SCM) system.
Creating an API design project from scratch in Anypoint Code Builder no longer spawns a corresponding design project in Design Center or creates a connection to the Anypoint SCM. For details, see Source Control for API Design Projects.
  * Set a business group for your API design project when you publish to Exchange instead of when you create the design project. For example, see the steps in Publish an API Spec to Exchange.


#### Configuration XML File Creation Enhancement
Anypoint Code Builder enables you to create one or more additional configuration XML files from within your integration or implementation projects. This feature is useful for adding an implementation for an interface. The feature also enables you to split complex project code into more manageable pieces. For more information, see Create an Additional Configuration XML File.
For more information, see Known Issues and Compatibility.
## December 6, 2023
Anypoint Code Builder releases a patch to Anypoint Extension Pack and the cloud IDE.
  * Extension pack version: 1.0.6
To use this extension pack in the desktop IDE, see Set up the Desktop IDE.
  * Cloud IDE version: 1.0.3
This cloud IDE version runs on the 1.0.6 extension pack.


The patch addresses the following issues:
Description | Issue  
---|---  
When you open the IDE, the exception `dw-lang-server-language-0" java.lang.NoClassDefFoundError: org/jboss/shrinkwrap/resolver/api/maven/Maven` in the **Mule DX Server** logs no longer occurs because of an open workspace that contains a non-Mule project, such as an API spec project or other folders or files.  
The issue `java.io.FileNotFoundException` no longer occurs due to attempted parsing of files that do not exist.  
After scaffolding an API spec into an interface within an implementation project, the IDE no longer produces the syntax validation issue `Configuration type reference is not compatible (INVALID_CONFIG_REFERENCE)` within the configuration XML for `config-ref` attribute-value pairs. Previously affected components include `<http:listener/>`, `<apikit:router/>`, and `<apikit:console/>`.  
A test connection no longer fails with the error `'Invalid Connection ElementDeclaration is declaring an extension: 'HTTP' that is not part of the session: '[]'` after you copy and paste an HTTP Listener configuration (`<http:listener-config/>`) into a new project.  
For more information, see Known Issues and Compatibility.
## October 19, 2023
Anypoint Code Builder releases a patch to the cloud IDE:
  * 1.0.2 (Cloud IDE): The cloud IDE removes the proxy for security purposes. URLs that trigger flows in the cloud IDE through the proxy no longer work. To trigger locally hosted flows that use an HTTP listener, see Triggering Flows in Your Development Environment.


There are no changes to the desktop IDE, which remains version 1.0.5.
## October 16, 2023
Anypoint Code Builder releases these versions:
  * 1.0.5 (Desktop IDE): Anypoint Code Builder for Desktop (desktop IDE) is generally available (GA) in this release.
  * 1.0.1 (Cloud IDE): The cloud IDE for Anypoint Code Builder remains in open beta:
Any use of an Anypoint Code Builder IDE in its beta state is subject to the applicable beta services terms and conditions, available from the cloud IDE.   
---  


The desktop IDE version 1.0.5 and cloud IDE version 1.0.1 both run on the same versions of the Anypoint Code Builder extensions, described in Change Log, and provide the same features.
To set up and gain access to the IDEs, see Getting Started with Anypoint Code Builder.
### What’s New
This release introduces:
  * Anypoint Extension Pack version 1.0.5 for the desktop IDE on VS Code Marketplace
  * API fragment support for JSON Schema
See Supported Specification Languages for API Fragments.


## Open Beta
Prior to the Oct 16, 2023 release, MuleSoft released these open beta versions of Anypoint Code Builder:
  * September 2023 (Open Beta)
  * August 2023 (Open Beta)
  * June 2023 (Open Beta)
  * April 24, 2023 (Open Beta)
  * April 2023 (Open Beta)


### 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.
  * Windows support on the desktop IDE. See Compatibility.
  * Hot deployments are supported for debugging Mule applications. See Hot Deploy When Debugging.
  * New export commands for packaging Mule applications within shareable and deployable JAR files. See Exporting Mule Projects.


### 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:
    * Secure configuration properties in your integrations and API implementations (see Defining and Securing Properties for a Mule Application)
    * Improvements to avoid reloading the IDE when unpacking the runtime for the first time


### 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 Getting Started with Anypoint Code Builder 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.
See Iteratively Design and Implement an API Specification for more information.
  * Updated UI canvas and code snippet support:
    * Directly import connectors from the canvas instead of using the dedicated command.
    * Use code snippets. See Working with Code Snippets for more information.
### 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 Getting Started with Anypoint Code Builder 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.
See Iteratively Design and Implement an API Specification for more information.
  * Updated UI canvas and code snippet support:
    * Directly import connectors from the canvas instead of using the dedicated command.
    * Use code snippets. See Working 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.
  * Search filters enable you to refine your search results when looking for an API asset from Anypoint Exchange. See Filtering Search Results for more information.
  * The canvas UI enables you to add components to flows in your integration.


## Compatibility
Application/Service | IDE | Version  
---|---|---  
Anypoint Platform | Desktop IDE | US clouds, EU clouds, and these Anypoint Platform instances on Hyperforce: Canada Cloud and Japan Cloud. (Not supported by MuleSoft Government Cloud or Anypoint Platform PCE)  
Anypoint Platform | Cloud IDE | US and EU clouds only  
Anypoint Platform | Both IDEs-Agentforce for Anypoint Code Builder Generative Flows | US clouds, EU clouds, and these Anypoint Platform instances on Hyperforce: Canada Cloud and Japan Cloud  
API Governance | Both IDEs | Validations for REST API and AsyncAPI specs  
CloudHub | Both IDEs | 1.0 and 2.0 (for deployments to the Sandbox environment)  
code-server | Cloud IDE | v4.17.1 (built-in)  
DataWeave | Both IDEs | Bundled with Mule runtime engine (built-in)  
Both IDEs | Multiple versions supported. See supported Mule and Java versions.  
Both IDEs | 3.9.4 (built-in)  
Mule runtime engine | Both IDEs | Multiple versions supported. See supported Mule and Java versions.  
Operating system | Desktop IDE | Windows 11, Windows 10, macOS Intel and ARM (M1 or M2)  
Visual Studio Code | Desktop IDE |  Minimum version: 1.88.1 Tested versions:
  * 1.96.4 or later (macOS)
  * 1.96.4 or later (Windows)

  
Web browser | Both IDEs | Browser Support for Anypoint Platform  
In Anypoint Code Builder, Mule applications for your implementation and integration projects are compatible with the following Mule runtime engine (Mule) and Java versions:
Supported Mule and Java versions:
Mule runtime version | Java version  
---|---  
Mule 4.9.x LTS  
Mule 4.8 Edge | Java 11, Java 17  
Mule 4.6.x LTS | Java 11, Java 17  
Mule 4.4  
Minor and major version changes to Mule require a manual update to your projects. Periodic Mule patch updates (such as from Mule 4.8.2 to 4.8.3) to Mule versions already downloaded to your IDE occur automatically when you log in to Anypoint Platform from the IDE.
## Known Issues
For new known issues and workarounds for this release, the May 27, 2025 release, the April 29, 2025 release, the March 21, 2025 release, and the February 6, 2025 release, see Salesforce Known Issues.
These known issues and workarounds from the December 9, 2024 release still apply to this release:
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. | W-14047707  
---|---  
When launching the cloud IDE for the first time from Anypoint Code Builder, you must allow popups.  
Previously configured sample data is overridden when selecting a component in the canvas UI. | W-16270847  
There is no command to delete dependencies related to assets that you import from Exchange to an API design project. Workaround: Remove the dependency from the `dependencies` node in the `exchange.json` file. | W-13822075  
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. | W-13172200  
Using autocompletion to create a parameter for the `value` field in the XML adds an extra `#[]` statement. | W-12444650  
Autocompletion does not work properly when more than one connector has the same prefix. | W-10667510  
Anypoint Connector for Apache Kafka (Apache Kafka Connector) does not display the **Test Connection** option. | W-12553536   
DataSense doesn’t identify functions provided by a connector. | W-12448776  
DataSense doesn’t reflect array structures at the payload’s root level. | W-12263085  
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. | W-11750473  
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. | W-12215165  
The Batch Job processor is not supported by the UI canvas or through auto-complete in the configuration XML.  
When scaffolding a GraphQL or AsyncAPI specification on Windows, an empty Mule configuration file with the name of the project is created in addition to the `flows.xml` file. Workaround: Delete the empty file. | W-15757808  
When source validation is enabled, AsyncAPI messages are invalid if `mediaType` doesn’t match the specification. | W-16663560  
When source validation is disabled, AsyncAPI messages are sent downstream without transforming `mediaType`. | W-16663585  
Source validation is not working with the Salesforce platform events `application/xml` content type. | W-16756836  
## See Also
  *   *   * Product Versioning and Back Support Policy