Merge branch 'MS2026-02-17-ACB' into W-20889415-custom-metadata-tm

Author: tasmoore

modules/ROOT/nav.adoc

@@ -12,6 +12,7 @@
 ** xref:start-add-folders.adoc[]
 ** xref:start-open-output-panel.adoc[]
 ** xref:start-scm.adoc[]
+** xref:start-workspaces.adoc[]
 
 // TUTORIALS
 * xref:tutorials.adoc[]

modules/ROOT/pages/_partials/acb-runtime-java.adoc

@@ -1,7 +1,7 @@
 
 //
 // tag::runtime-java-download[]
-You can select any of the supported Mule runtime and Java versions. The IDE saves your version settings to the project's `mule-artifact.json` file.
+You can select from locally available Mule runtime and Java versions. The dropdown shows only the Mule runtime versions that are installed on your local disk, including bundled Mule runtime versions that are available immediately after installation. The IDE saves your version settings to the project's `mule-artifact.json` file. Bundled Mule runtime versions enable instant project opening and design. To install additional Mule runtime versions, use the `MuleSoft: Install Runtime` command.
 // end::runtime-java-download[]
 //
 //
@@ -19,7 +19,7 @@ To set default Mule runtime and Java versions for the projects you create, see x
 
 //
 // tag::runtime-java-notification[]
-The IDE provides a notification if it is necessary to download the selected Mule runtime or Java version for the project. Mule runtime downloads to `${user.home}/AnypointCodeBuilder/runtimes`, and the selected Java version downloads to `${user.home}/AnypointCodeBuilder/java`.
+Projects open instantly using the bundled Mule runtime versions. The IDE provides a notification only if you must download a specific Mule runtime version or Java version for running or debugging your application. The Mule runtime versions download to `${user.home}/AnypointCodeBuilder/runtimes`, and the selected Java version downloads to `${user.home}/AnypointCodeBuilder/java`.
 // end::runtime-java-notification[]
 //
 

modules/ROOT/pages/_partials/af-shared.adoc

@@ -97,7 +97,7 @@ See xref:anypoint-code-builder::af-get-started.adoc#setup-space[Set Up the Priva
 
 Now you're ready to create an agent network project. Choose one of these methods.
 
-* xref:anypoint-code-builder::af-create-agent-network.adoc#create-dev-agent[Create a Network Using MuleSoft Dev Agent]
+* xref:anypoint-code-builder::af-create-agent-network.adoc#create-dev-agent[Create a Network Using MuleSoft Vibes]
 * xref:anypoint-code-builder::af-create-agent-network.adoc#create-acb[Create a Network Using Anypoint Code Builder]
 * xref:anypoint-code-builder::af-create-agent-network.adoc#create-cli[Create a Network Using the Anypoint CLI]
 
@@ -106,15 +106,15 @@ Now you're ready to create an agent network project. Choose one of these methods
 
 After you create your agent network project, configure `agent-network.yaml` and `exchange.json` to reflect the structure of your network.
 
-* xref:anypoint-code-builder::af-define-your-agent-network-specification.adoc#define-dev-agent[Define a Network Using MuleSoft Dev Agent]
+* xref:anypoint-code-builder::af-define-your-agent-network-specification.adoc#define-dev-agent[Define a Network Using MuleSoft Vibes]
 * xref:anypoint-code-builder::af-define-your-agent-network-specification.adoc#define-acb-ide[Define a Network Using Anypoint Code Builder or IDE]
 
 [[step-4-publish]]
 === Step 4: Publish Your Agent Network Assets
 
 Build and publish your agent network project as Anypoint Exchange assets. When you publish the agent network, an asset is created in Exchange for each broker, agent, and MCP server that's in your agent network.
 
-* xref:anypoint-code-builder::af-publish-agent-network-assets.adoc#publish-dev-agent[Publish Your Network Using MuleSoft Dev Agent]
+* xref:anypoint-code-builder::af-publish-agent-network-assets.adoc#publish-dev-agent[Publish Your Network Using MuleSoft Vibes]
 * xref:anypoint-code-builder::af-publish-agent-network-assets.adoc#publish-acb[Publish Your Network Using Anypoint Code Builder]
 * xref:anypoint-code-builder::af-build-agent-networks-in-a-ci-cd-environment.adoc#agent-network-project-publish[Publish Your Network Using the Anypoint CLI]
 
@@ -123,7 +123,7 @@ Build and publish your agent network project as Anypoint Exchange assets. When y
 
 Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 private space or to a Runtime Fabric (limited availability).
 
-* xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-dev-agent[Deploy Your Network Using the MuleSoft Dev Agent]
+* xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-dev-agent[Deploy Your Network Using MuleSoft Vibes]
 * xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-acb[Deploy Your Network Using Anypoint Code Builder]
 * xref:anypoint-code-builder::af-build-agent-networks-in-a-ci-cd-environment.adoc#agent-network-project-deploy[Deploy Your Network Using the Anypoint CLI]
 // end::get-started[]

modules/ROOT/pages/acb-external-libraries.adoc

@@ -0,0 +1,92 @@
+= Configure External Libraries for Mule Projects
+:page-deployment-options: cloud-ide, desktop-ide
+
+External libraries are project-level dependencies that Mule applications require to support certain connectors and components, such as Database connectors or Spring-based components.
+Anypoint Code Builder provides a guided interface to add, edit, and delete external libraries, and automatically manages the corresponding entries in the project POM file.
+
+External library configurations apply at the project level. Any change to a configured library affects all components in the project that require that library.
+
+== Before You Begin
+
+* xref:start-acb.adoc[].
+* xref:int-create-integrations.adoc[].
+* Add a connector or component that requires an external library, such as a Database or Spring component.
+
+== When You Need to Configure an External Library
+
+Anypoint Code Builder prompts you to configure an external library when you add or configure a component that requires additional dependencies.
+For example, this can occur when you:
+
+* Add a Database connector connection
+* Configure a Spring-based component
+* Use a custom component that depends on external libraries
+
+You can also manage external libraries from the project-level configuration, independent of a specific component.
+
+== Add an External Library
+
+You can add an external library from the component configuration or from the project-level library configuration interface.
+
+Add external libraries from one of these sources:
+
+* Recommended libraries
+* Maven dependencies
+* Local files
+
+Open the library configuration interface from a component:
+
+. In the canvas, select a component that requires an external library.
+. In the component configuration panel, locate the *Required Libraries* list.
+. Click the *Configure library* icon.
++
+Anypoint Code Builder opens the *Library Configuration* page.
+Changes made on this page apply to the entire project.
+
+=== Add a Recommended Library
+
+Some components provide recommended libraries that match the component requirements.
+
+. Open the *Library Configuration* page.
+. Select *Recommended Library*.
++
+The interface shows the library to add to the project.
+. Click *Apply*.
++
+The IDE adds the recommended library to the project POM file and applies it to all components that require it.
+
+=== Add a Maven Dependency
+
+Search Maven Central or manually specify Maven coordinates to add a dependency.
+
+. Open the *Library Configuration* page.
+. Select *Maven Dependency*.
+. In the *Search Maven Central Repository* field, search for a dependency or enter the required Maven fields manually.
+. Specify values for *Group ID*, *Artifact ID*, and *Version*.
+. Optionally, configure additional fields such as *Scope*.
+. Click *Apply*.
+
+Only libraries that meet the required criteria appear in component library fields after configuration.
+
+=== Add a Library from a Local File
+
+Add a dependency from a local file, such as a JAR or an external POM file.
+
+. Open the *Library Configuration* page.
+. Select *Local File*.
+. Select a file from your system.
++
+Anypoint Code Builder automatically populates the Maven fields based on the selected file.
+. Override the populated values if required.
+. Click *Apply*.
+
+If you select an external POM file, it takes precedence over any POM embedded in the artifact file.
+
+== Edit or Delete an External Library
+
+Edit or remove an existing library configuration.
+
+. Open the *Library Configuration* page.
+. Select the configured library.
+. Use the available actions to update or delete the library.
++
+Deleting a library removes it from the project POM file and affects all components that use the library.

modules/ROOT/pages/af-agent-networks.adoc

@@ -6,7 +6,7 @@ Complex tasks often require a series of steps, with each step handled by a diffe
 
 Define your agent network in a simple, human-readable YAML file in Anypoint Code Builder. This approach abstracts away the underlying technical complexities so you focus on the business constraints and context of your process without needing to understand the inner workings of the orchestration engine.
 
-Don't worry, we give you a head start by providing you with a YAML template in your agent network project. MuleSoft Dev Agent can help you configure it for your business environment, publish agent network assets to Anypoint Exchange, and deploy your agent network instance.
+Don't worry, we give you a head start by providing you with a YAML template in your agent network project. MuleSoft Vibes can help you configure it for your business environment, publish agent network assets to Anypoint Exchange, and deploy your agent network instance.
 
 For more information about Agent Fabric, see xref:agent-fabric::index.adoc[].
 

modules/ROOT/pages/af-create-agent-network.adoc

@@ -1,20 +1,20 @@
 [[create-networks]]
 = Create Agent Networks
 
-Whether you want to use MuleSoft Dev Agent or the UI, Anypoint Code Builder includes all the agent network functionality you need to get started.
+Whether you want to use MuleSoft Vibes or the UI, Anypoint Code Builder includes all the agent network functionality you need to get started.
 
 [[before-you-begin]]
 == Before You Begin 
 
 Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites].
 
 [[create-dev-agent]]
-== Create a Network Using the MuleSoft Dev Agent
+== Create a Network Using MuleSoft Vibes
 
-MuleSoft Dev Agent can help you create your project. For more information about MuleSoft Dev Agent, see xref:anypoint-code-builder::api-ai-create-spec.adoc[Creating API Specs with MuleSoft Dev Agent].
+MuleSoft Vibes can help you create your project. For more information, see xref:anypoint-code-builder::api-ai-create-spec.adoc[].
 
 . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
-. Describe your agent network, including the brokers, agents, MCP servers, and LLMs you want to connect. MuleSoft Dev Agent does the rest.
+. Describe your agent network, including the brokers, agents, MCP servers, and LLMs you want to connect. MuleSoft Vibes does the rest.
 
 To get started try one of these suggested prompts.
 
@@ -55,3 +55,4 @@ If you run operations within a CI/CD environment, you can use Anypoint CLI's plu
 == See Also
 
 * xref:af-define-your-agent-network-specification.adoc[]
+* xref:start-workspaces.adoc[]

modules/ROOT/pages/af-define-your-agent-network-specification.adoc

@@ -12,9 +12,9 @@ Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites
 To help you identify agents that are also brokers on the Anypoint Code Builder canvas, consider appending "Broker" to the end of the name, for example `employee-onboarding-broker`.
 
 [[define-dev-agent]]
-== Define a Network Using MuleSoft Dev Agent
+== Define a Network Using MuleSoft Vibes
 
-MuleSoft Dev Agent can help you configure your agent network specification. For more information about MuleSoft Dev Agent, see xref:anypoint-code-builder::api-ai-create-spec.adoc[Creating API Specs with MuleSoft Dev Agent].
+MuleSoft Vibes can help you configure your agent network specification. For more information, see xref:anypoint-code-builder::api-ai-create-spec.adoc[].
 
 . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
 . Give the agent information about your agent network, including the brokers, agents, MCP servers, and LLMs you want to connect.
@@ -29,7 +29,7 @@ To get started try one of these suggested prompts.
 [[define-acb-ide]]
 == Define a Network Using Anypoint Code Builder or IDE
 
-If you don't want to use MuleSoft Dev Agent, use Anypoint Code Builder or your IDE to edit the `agent-network.yaml` and `exchange.json` files and define your agent network and authentication.
+If you don't want to use MuleSoft Vibes, use Anypoint Code Builder or your IDE to edit the `agent-network.yaml` and `exchange.json` files and define your agent network and authentication.
 
 To understand sections of the project files and expected values, see xref:anypoint-code-builder::af-project-files.adoc[Agent Network Project File Reference]. The agent-network.yaml file can contain definitions for one or more brokers.
 
@@ -42,10 +42,10 @@ Use auto-completion menus in Anypoint Code Builder to speed your development. Fo
 
 If you have existing Exchange assets you want to use in your agent network, add them to the dependencies attribute in `exchange.json` in your project. After you add assets, edit the `agent-network.yaml` file to indicate which brokers use those assets.
 
-=== Add Assets Using MuleSoft Dev Agent
+=== Add Assets Using MuleSoft Vibes
 
 . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
-. Tell the agent that you want to add Exchange assets to your project. MuleSoft Dev Agent does the rest.
+. Tell the agent that you want to add Exchange assets to your project. MuleSoft Vibes does the rest.
 
 To get started try one of these suggested prompts.
 

modules/ROOT/pages/af-deploy-agent-network-targets.adoc

@@ -44,12 +44,12 @@ Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites
 When you deploy your agent network, an instance is deployed for each connection defined in your agent network. If your agent network contains brokers, an instance is deployed per broker.
 
 [[deploy-dev-agent]]
-== Deploy Your Network Using the MuleSoft Dev Agent
+== Deploy Your Network Using MuleSoft Vibes
 
-MuleSoft Dev Agent can help you deploy your agent network instances. For more information about MuleSoft Dev Agent, see xref:anypoint-code-builder::api-ai-create-spec.adoc[Creating API Specs with MuleSoft Dev Agent].
+MuleSoft Vibes can help you deploy your agent network instances. For more information, see xref:anypoint-code-builder::api-ai-create-spec.adoc[].
 
 . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
-. Tell the agent that you want to deploy your agent network. MuleSoft Dev Agent does the rest.
+. Tell the agent that you want to deploy your agent network. MuleSoft Vibes does the rest.
 
 To get started, try one of these suggested prompts.
 

modules/ROOT/pages/af-publish-agent-network-assets.adoc

@@ -13,12 +13,12 @@ Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites
 If you want to publish your project assets to a different business group, update the relevant `groupId` in `exchange.json`.
 
 [[publish-dev-agent]]
-== Publish Your Network Using MuleSoft Dev Agent
+== Publish Your Network Using MuleSoft Vibes
 
-MuleSoft Dev Agent can help you publish your agent network specification to Anypoint Exchange. For more information about MuleSoft Dev Agent, see xref:anypoint-code-builder::api-ai-create-spec.adoc[Creating API Specs with MuleSoft Dev Agent].
+MuleSoft Vibes can help you publish your agent network specification to Anypoint Exchange. For more information, see xref:anypoint-code-builder::api-ai-create-spec.adoc[].
 
 . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
-. Tell the agent that you want to publish your agent network. MuleSoft Dev Agent does the rest.
+. Tell the agent that you want to publish your agent network. MuleSoft Vibes does the rest.
 
 To get started try one of these suggested prompts.
 

modules/ROOT/pages/des-create-api-specs.adoc

@@ -283,9 +283,11 @@ If you created an OAS 3.0 (YAML) project, you can replace the initial spec with
 
 == See Also
 
+
 * xref:start-acb.adoc[]
 * xref:tutorials.adoc[]
 * xref:access-management::business-groups.adoc[]
 * xref:start-discover-ui.adoc#use-autocomplete[Use Auto-Complete in the Editors]
 * xref:tut-af-design-am-flights-api.adoc[] Tutorial
-* xref:des-delete-api-projects.adoc[]
+* xref:des-delete-api-projects.adoc[]
+* xref:start-workspaces.adoc[]