Skip to content

Commit 094ac28

Browse files
W-21232676-Rename-Dev-Agent-to-MuleSoft-Vibes-CP
1 parent 010f7e6 commit 094ac28

8 files changed

Lines changed: 40 additions & 40 deletions

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ See xref:anypoint-code-builder::af-get-started.adoc#setup-space[Set Up the Priva
9797

9898
Now you're ready to create an agent network project. Choose one of these methods.
9999

100-
* xref:anypoint-code-builder::af-create-agent-network.adoc#create-dev-agent[Create a Network Using MuleSoft Dev Agent]
100+
* xref:anypoint-code-builder::af-create-agent-network.adoc#create-dev-agent[Create a Network Using MuleSoft Vibes]
101101
* xref:anypoint-code-builder::af-create-agent-network.adoc#create-acb[Create a Network Using Anypoint Code Builder]
102102
* xref:anypoint-code-builder::af-create-agent-network.adoc#create-cli[Create a Network Using the Anypoint CLI]
103103

@@ -106,15 +106,15 @@ Now you're ready to create an agent network project. Choose one of these methods
106106

107107
After you create your agent network project, configure `agent-network.yaml` and `exchange.json` to reflect the structure of your network.
108108

109-
* xref:anypoint-code-builder::af-define-your-agent-network-specification.adoc#define-dev-agent[Define a Network Using MuleSoft Dev Agent]
109+
* xref:anypoint-code-builder::af-define-your-agent-network-specification.adoc#define-dev-agent[Define a Network Using MuleSoft Vibes]
110110
* xref:anypoint-code-builder::af-define-your-agent-network-specification.adoc#define-acb-ide[Define a Network Using Anypoint Code Builder or IDE]
111111

112112
[[step-4-publish]]
113113
=== Step 4: Publish Your Agent Network Assets
114114

115115
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.
116116

117-
* xref:anypoint-code-builder::af-publish-agent-network-assets.adoc#publish-dev-agent[Publish Your Network Using MuleSoft Dev Agent]
117+
* xref:anypoint-code-builder::af-publish-agent-network-assets.adoc#publish-dev-agent[Publish Your Network Using MuleSoft Vibes]
118118
* xref:anypoint-code-builder::af-publish-agent-network-assets.adoc#publish-acb[Publish Your Network Using Anypoint Code Builder]
119119
* 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]
120120

@@ -123,7 +123,7 @@ Build and publish your agent network project as Anypoint Exchange assets. When y
123123

124124
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).
125125

126-
* xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-dev-agent[Deploy Your Network Using the MuleSoft Dev Agent]
126+
* xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-dev-agent[Deploy Your Network Using MuleSoft Vibes]
127127
* xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-acb[Deploy Your Network Using Anypoint Code Builder]
128128
* 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]
129129
// end::get-started[]

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Complex tasks often require a series of steps, with each step handled by a diffe
66

77
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.
88

9-
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.
9+
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.
1010

1111
For more information about Agent Fabric, see xref:agent-fabric::index.adoc[].
1212

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
[[create-networks]]
22
= Create Agent Networks
33

4-
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.
4+
Whether you want to use MuleSoft Vibes or the UI, Anypoint Code Builder includes all the agent network functionality you need to get started.
55

66
[[before-you-begin]]
77
== Before You Begin
88

99
Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites].
1010

1111
[[create-dev-agent]]
12-
== Create a Network Using the MuleSoft Dev Agent
12+
== Create a Network Using MuleSoft Vibes
1313

14-
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].
14+
MuleSoft Vibes can help you create your project. For more information, see xref:anypoint-code-builder::api-ai-create-spec.adoc[].
1515

1616
. In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
17-
. Describe your agent network, including the brokers, agents, MCP servers, and LLMs you want to connect. MuleSoft Dev Agent does the rest.
17+
. Describe your agent network, including the brokers, agents, MCP servers, and LLMs you want to connect. MuleSoft Vibes does the rest.
1818

1919
To get started try one of these suggested prompts.
2020

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites
1212
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`.
1313

1414
[[define-dev-agent]]
15-
== Define a Network Using MuleSoft Dev Agent
15+
== Define a Network Using MuleSoft Vibes
1616

17-
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].
17+
MuleSoft Vibes can help you configure your agent network specification. For more information, see xref:anypoint-code-builder::api-ai-create-spec.adoc[].
1818

1919
. In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
2020
. 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.
2929
[[define-acb-ide]]
3030
== Define a Network Using Anypoint Code Builder or IDE
3131

32-
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.
32+
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.
3333

3434
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.
3535

@@ -42,10 +42,10 @@ Use auto-completion menus in Anypoint Code Builder to speed your development. Fo
4242

4343
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.
4444

45-
=== Add Assets Using MuleSoft Dev Agent
45+
=== Add Assets Using MuleSoft Vibes
4646

4747
. In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
48-
. Tell the agent that you want to add Exchange assets to your project. MuleSoft Dev Agent does the rest.
48+
. Tell the agent that you want to add Exchange assets to your project. MuleSoft Vibes does the rest.
4949

5050
To get started try one of these suggested prompts.
5151

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,12 +44,12 @@ Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites
4444
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.
4545

4646
[[deploy-dev-agent]]
47-
== Deploy Your Network Using the MuleSoft Dev Agent
47+
== Deploy Your Network Using MuleSoft Vibes
4848

49-
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].
49+
MuleSoft Vibes can help you deploy your agent network instances. For more information, see xref:anypoint-code-builder::api-ai-create-spec.adoc[].
5050

5151
. In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
52-
. Tell the agent that you want to deploy your agent network. MuleSoft Dev Agent does the rest.
52+
. Tell the agent that you want to deploy your agent network. MuleSoft Vibes does the rest.
5353

5454
To get started, try one of these suggested prompts.
5555

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,12 +13,12 @@ Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites
1313
If you want to publish your project assets to a different business group, update the relevant `groupId` in `exchange.json`.
1414

1515
[[publish-dev-agent]]
16-
== Publish Your Network Using MuleSoft Dev Agent
16+
== Publish Your Network Using MuleSoft Vibes
1717

18-
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].
18+
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[].
1919

2020
. In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
21-
. Tell the agent that you want to publish your agent network. MuleSoft Dev Agent does the rest.
21+
. Tell the agent that you want to publish your agent network. MuleSoft Vibes does the rest.
2222

2323
To get started try one of these suggested prompts.
2424

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
= Developing Integrations Using MuleSoft Dev Agent
1+
= Developing Integrations Using MuleSoft Vibes
22
:page-deployment-options: cloud-ide, desktop-ide
33

4-
To develop, manage, or maintain your applications, use MuleSoft Dev Agent in Anypoint Code Builder. MuleSoft Dev Agent is a purpose-built assistant for the development lifecycle, available directly in the IDE. It integrates with the xref:mulesoft-mcp-server::index.adoc[MuleSoft MCP Server] and supports many capabilities, such as:
4+
To develop, manage, or maintain your applications, use MuleSoft Vibes in Anypoint Code Builder. It is a purpose-built assistant for the development lifecycle, available directly in the IDE. It integrates with the xref:mulesoft-mcp-server::index.adoc[MuleSoft MCP Server] and supports many capabilities, such as:
55

66
* Developing API specifications
77
* Creating and configuring applications
@@ -10,7 +10,7 @@ To develop, manage, or maintain your applications, use MuleSoft Dev Agent in Any
1010
1111
All of these actions are driven by natural language prompts.
1212

13-
When you generate an integration, MuleSoft Dev Agent transforms your business logic into a Mule application. The generated application includes:
13+
When you generate an integration, MuleSoft Vibes transforms your business logic into a Mule application. The generated application includes:
1414

1515
* Flows
1616
* Connector configurations
@@ -19,7 +19,7 @@ When you generate an integration, MuleSoft Dev Agent transforms your business lo
1919
2020
These capabilities are powered by large language models (LLMs) that run within the Salesforce Shared Trust Boundary.
2121

22-
NOTE: MuleSoft Dev Agent is available on US, EU, Canada, and Japan cloud hosts.
22+
NOTE: MuleSoft Vibes is available on US, EU, Canada, and Japan cloud hosts.
2323

2424
[[before-you-begin]]
2525
== Before You Begin
@@ -28,33 +28,33 @@ Before you start creating your API spec, make sure you meet the following prereq
2828

2929
* xref:start-acb.adoc[Set up and access the web or desktop IDE].
3030
* Make sure you have the xref:start-configure-permissions.adoc#permissions[required Anypoint Code Builder permissions].
31-
* Ensure you have the following permissions to use MuleSoft Dev Agent:
31+
* Ensure you have the following permissions to use MuleSoft Vibes:
3232
** *Mule Developer Generative AI User*
3333
* Make sure Einstein is enabled in Access Management. For more information, see xref:access-management::enabling-einstein.adoc[Enabling Einstein for Anypoint Platform].
3434

35-
NOTE: MuleSoft Dev Agent always uses the permissions of the Anypoint Platform user who is logged into Anypoint Code Builder, and can only execute actions that the authenticated user has permission to perform in Anypoint Platform.
35+
NOTE: MuleSoft Vibes always uses the permissions of the Anypoint Platform user who is logged into Anypoint Code Builder, and can only execute actions that the authenticated user has permission to perform in Anypoint Platform.
3636

37-
== Unified Dev Agent Experience
37+
== Unified MuleSoft Vibes Experience
3838

39-
MuleSoft Dev Agent provides a single panel where you can develop integrations and API specifications. Unlike earlier versions of generative features, Dev Agent does not insert output through a separate panel. Instead, it writes directly into your project files when you grant edit permissions.
39+
MuleSoft Vibes provides a single panel where you can develop integrations and API specifications. Unlike earlier versions of generative features, it does not insert output through a separate panel. Instead, it writes directly into your project files when you grant edit permissions.
4040

41-
Depending on your settings, Dev Agent can:
41+
Depending on your settings, MuleSoft Vibes can:
4242

4343
* Request approval before writing to your files.
44-
* Write automatically if *Auto-approve* is enabled in the Dev Agent settings.
44+
* Write automatically if *Auto-approve* is enabled in the MuleSoft Vibes settings.
4545

4646
For details on configuring permissions and server connections, see xref:troubleshoot-generative-ai.adoc[].
4747

4848
== Provide Additional Context
4949

50-
You can improve the accuracy of generated outputs by adding extra context to Dev Agent.
51-
In addition to prompts, Dev Agent accepts the following types of input:
50+
You can improve the accuracy of generated outputs by adding extra context to MuleSoft Vibes.
51+
In addition to prompts, it accepts the following types of input:
5252

5353
* **Files** – Add a requirements file or other reference documents.
54-
* **Folders** – Provide an entire project folder for Dev Agent to consider.
54+
* **Folders** – Provide an entire project folder for MuleSoft Vibes to consider.
5555
* **Terminal Input** – Share terminal outputs as context for the request.
5656

57-
This context helps Dev Agent generate flows and API specifications that align more closely with your requirements.
57+
This context helps MuleSoft Vibes generate flows and API specifications that align more closely with your requirements.
5858

5959
== Trust Layer
6060

@@ -63,7 +63,7 @@ The Einstein trust layer bridges Anypoint Platform and the LLMs, as shown in thi
6363
image::acb-einstein-trust-layer.png["Flow depicting how the trust layer works, including the steps of the flow"]
6464

6565
[calloutlist]
66-
. You create a message based on your use case and send it to Dev Agent.
66+
. You create a message based on your use case and send it to MuleSoft Vibes.
6767
. To minimize inaccurate responses, messages are grounded with MuleSoft proprietary data and user context.
6868
. To ensure safe data transfer to external LLMs, the message is sent via a secure gateway.
6969
. All data remains within Salesforce-managed boundaries.
@@ -76,5 +76,5 @@ This feature uses AI models that can produce inaccurate or harmful responses. Re
7676

7777
== See Also
7878

79-
* xref:troubleshooting.adoc[Troubleshooting Dev Agent]
80-
* xref:api-ai-create-spec.adoc[Creating API Specs with Dev Agent]
79+
* xref:troubleshooting.adoc[]
80+
* xref:api-ai-create-spec.adoc[]

modules/ROOT/pages/vibes-get-started.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1-
= Get Started with MuleSoft Dev Agent
1+
= Get Started with MuleSoft Vibes
22
:page-aliases: a4d-get-started.adoc
33

44
MuleSoft Vibes helps you build APIs and integrations using natural language prompts directly in your development environment.
55

6-
== Use MuleSoft Dev Agent
6+
== Use MuleSoft Vibes
77

88
You can open MuleSoft Vibes from the:
99

@@ -53,7 +53,7 @@ For more information about how MuleSoft’s AI generation pipelines work, see th
5353

5454
== Provide MuleSoft Vibes with Context
5555

56-
You can improve the accuracy of MuleSoft MuleSoft Vibes output by providing additional context files or inputs.
56+
You can improve the accuracy of MuleSoft Vibes output by providing additional context files or inputs.
5757
Examples include requirement files (`requirements.txt`), configuration folders, logs, URLs, or terminal output.
5858

5959
To add context:

0 commit comments

Comments
 (0)