mulesoft · Cristian-Venticinque · May 6, 2026 · May 8, 2026 · May 8, 2026
@@ -65,6 +65,7 @@
 ** xref:vibes-skills.adoc[]
 ** xref:vibes-api-ai-create-spec.adoc[]
 ** xref:vibes-create-integrations.adoc[]
+** xref:vibes-run-multiple-integration-projects-locally.adoc[]
 ** xref:vibes-prompt-examples.adoc[]
 ** xref:troubleshoot-generative-ai.adoc[]
 

@@ -227,6 +227,13 @@ MuleSoft: Re-scaffold this local API
 MuleSoft: Run Governance Validation with all Rulesets and Rules
 ----
 
+* Run a saved multi-project launch configuration from your workspace. See xref:vibes-run-multiple-integration-projects-locally.adoc[].
++
+[source,command]
+----
+MuleSoft: Run Multi-Project Configuration
+----
+
 
 //
 //TESTED: 05/20/24 - HIDING: don't see it in command palette

@@ -1,4 +1,4 @@
-= Troubleshoot AI Features in Anypoint Code Builder
+= Troubleshooting AI Features in Anypoint Code Builder
 
 The following errors sometimes occur when you use MuleSoft Vibes in Anypoint Code Builder.
 

@@ -1,4 +1,4 @@
-= Use Checkpoints to Track Changes
+= Tracking Changes with Checkpoints
 :page-aliases: a4d-checkpoints.adoc
 
 When you have a folder or directory open in Visual Studio Code, you can use checkpoints to track changes to your workspace.

@@ -1,4 +1,4 @@
-= View Conversation History
+= Viewing Conversation History
 
 MuleSoft Vibes allows you to return to tasks you have previously started and continue working from where you left off.
 
@@ -38,7 +38,7 @@ You can remove past tasks in two ways:
 
 MuleSoft Vibes automatically summarizes conversation history to reduce total token consumption while preserving relevant context.
 
-As tasks grow in complexity, conversation history becomes larger. Instead of sending the full history with each interaction, Vibes compacts previous messages into summaries. This maintains performance and reduces tokens usage.
+As tasks grow in complexity, conversation history becomes larger. Instead of sending the full history with each interaction, Vibes compacts previous messages into summaries. This maintains performance and reduces tokens usage.
 
 Chat history summaries:
 

@@ -1,4 +1,4 @@
-= Get Started with MuleSoft Vibes
+= Getting Started with MuleSoft Vibes
 :page-aliases: a4d-get-started.adoc
 
 MuleSoft Vibes helps you build APIs and integrations using natural language prompts directly in your development environment.

@@ -1,4 +1,4 @@
-= Configure an MCP Server
+= Configuring an MCP Server
 :page-aliases: a4d-mcp-server.adoc
 
 Add and manage MCP servers in Anypoint Code Builder to extend MuleSoft Vibes with tools for API design, integrations, governance, and agent networks. 

@@ -0,0 +1,110 @@
+= Running Multiple Local Integration Projects with MuleSoft Vibes
+:page-deployment-options: cloud-ide, desktop-ide
+
+Run multiple integration projects locally in one runtime to validate service-to-service behavior before deployment. Use MuleSoft Vibes to create a reusable run configuration automatically, start related projects together, and test end-to-end behavior. Update and reuse the same configuration as your local integration scope changes.
+
+When an integration depends on multiple local Mule projects, starting each project manually can slow down validation and increase setup errors. MuleSoft Vibes can create a run configuration from your prompt and execute all selected projects together in the same local runtime instance.
+
+Multi-project configurations use the default runtime arguments defined in Anypoint Code Builder settings (`Mule > Runtime: Default Arguments`).
+
+== Before You Begin
+
+* xref:start-workspaces.adoc[Work in a multi-root workspace] that contains the related Mule projects.
+* xref:mulesoft-vibes.adoc[Set up MuleSoft Vibes] and confirm you have required permissions.
+* Verify that each project can run locally in your IDE environment.
+
+== Run Related Projects Together Locally
+
+Use MuleSoft Vibes to create and run a reusable local run configuration for the projects that participate in your flow.
+
+. Open MuleSoft Vibes.
+. Enter a prompt that identifies the projects to run together.
++
+Example prompts:
++
+* `Create and run a local configuration for main-project, project-one, and project-two.`
+* `Run all projects in this workspace.`
+* `Run all my projects in debug mode.`
+. Review the plan if you are working in Plan mode, and then run the task.
+. Wait for MuleSoft Vibes to create the run configuration and start the selected projects.
+. Confirm that the projects are running in the same local runtime instance.
+
+== Run Saved Configurations from the IDE
+
+After MuleSoft Vibes creates a multi-project configuration, you can reuse it through standard IDE execution paths.
+
+. Open the *Run and Debug* panel.
+. Select the saved multi-project configuration from the launch configuration list.
+. Run it from the launch menu.
++
+You can also run the same saved configuration from the Command Palette with `MuleSoft: Run Multi-Project Configuration`.
+
+== Create and Update Configurations for Debugging
+
+You can create or update multi-project configurations for either run mode or debug mode.
+
+. Ask MuleSoft Vibes to run your projects in debug mode when you need to inspect flow execution.
+. If needed, update an existing configuration to change the execution mode.
++
+Example prompts:
++
+* `Run all my projects in debug mode.`
+* `Change my configuration to debug mode.`
+
+== Verify End-to-End Integration Behavior
+
+After MuleSoft Vibes starts the projects, validate the integration behavior from the entry-point project.
+
+. Call an endpoint in your main project.
+. Confirm that downstream project responses are returned as expected.
+. Verify that the final response includes the combined or orchestrated output for your flow.
+
+== Update and Reuse a Saved Configuration
+
+When your integration scenario changes, ask MuleSoft Vibes to update the existing configuration instead of recreating setup steps manually.
+
+. In MuleSoft Vibes, request an update to the saved configuration.
++
+Example prompts:
++
+* `Update my local run configuration to include only project-one and project-two.`
+* `Rename this local run configuration to project-one-two flow validation.`
+* `Change my configuration to debug mode.`
+. Run the saved configuration again for the next validation cycle.
+. Repeat updates as your project set changes.
+
+== Set Explicit Mule and JDK Versions
+
+By default, a multi-project configuration uses the latest compatible Mule runtime and JDK versions that are available locally for execution. If your validation requires exact versions, edit the generated launch configuration in your `.code-workspace` file and specify them explicitly.
+
+. Open your `.code-workspace` file.
+. Locate the generated multi-project launch configuration.
+. Add explicit values for `mule.runtime.version` and `mule.jdk.version`.
++
+For example:
++
+[source,json]
+----
+{
+  "type": "mule-xml-debugger",
+  "request": "launch",
+  "name": "Run All 3 Projects (Explicit Versions)",
+  "noDebug": true,
+  "mule.projects": [
+    "${workspaceFolder:test-run-config}",
+    "${workspaceFolder:test-project1}",
+    "${workspaceFolder:test-project2}"
+  ],
+  "mule.runtime.version": "4.8.2",
+  "mule.jdk.version": "17"
+}
+----
+
+== See Also
+
+* xref:vibes-get-started.adoc[]
+* xref:start-workspaces.adoc[]
+* xref:int-debug-mule-apps.adoc[]
+* xref:int-versions.adoc[]
+* xref:ref-mule-settings.adoc[]
+* xref:int-create-secure-configs.adoc[].
@@ -1,4 +1,4 @@
-= Use Skills with MuleSoft Vibes
+= Using Skills with MuleSoft Vibes
 :page-deployment-options: cloud-ide, desktop-ide
 
 Skills are reusable instruction sets that MuleSoft Vibes activates only when they apply to your task. Each skill packages guidance and optional resources so MuleSoft Vibes can follow a consistent workflow without loading that material for unrelated prompts.