You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/_partials/af-shared.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ See xref:anypoint-code-builder::af-get-started.adoc#setup-space[Set Up the Priva
97
97
98
98
Now you're ready to create an agent network project. Choose one of these methods.
99
99
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]
101
101
* xref:anypoint-code-builder::af-create-agent-network.adoc#create-acb[Create a Network Using Anypoint Code Builder]
102
102
* xref:anypoint-code-builder::af-create-agent-network.adoc#create-cli[Create a Network Using the Anypoint CLI]
103
103
@@ -106,15 +106,15 @@ Now you're ready to create an agent network project. Choose one of these methods
106
106
107
107
After you create your agent network project, configure `agent-network.yaml` and `exchange.json` to reflect the structure of your network.
108
108
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]
110
110
* xref:anypoint-code-builder::af-define-your-agent-network-specification.adoc#define-acb-ide[Define a Network Using Anypoint Code Builder or IDE]
111
111
112
112
[[step-4-publish]]
113
113
=== Step 4: Publish Your Agent Network Assets
114
114
115
115
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.
116
116
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]
118
118
* xref:anypoint-code-builder::af-publish-agent-network-assets.adoc#publish-acb[Publish Your Network Using Anypoint Code Builder]
119
119
* 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]
120
120
@@ -123,7 +123,7 @@ Build and publish your agent network project as Anypoint Exchange assets. When y
123
123
124
124
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).
125
125
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]
127
127
* xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-acb[Deploy Your Network Using Anypoint Code Builder]
128
128
* 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]
Copy file name to clipboardExpand all lines: modules/ROOT/pages/af-agent-networks.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Complex tasks often require a series of steps, with each step handled by a diffe
6
6
7
7
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.
8
8
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.
10
10
11
11
For more information about Agent Fabric, see xref:agent-fabric::index.adoc[].
Copy file name to clipboardExpand all lines: modules/ROOT/pages/af-create-agent-network.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
[[create-networks]]
2
2
= Create Agent Networks
3
3
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.
5
5
6
6
[[before-you-begin]]
7
7
== Before You Begin
8
8
9
9
Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites].
10
10
11
11
[[create-dev-agent]]
12
-
== Create a Network Using the MuleSoft Dev Agent
12
+
== Create a Network Using MuleSoft Vibes
13
13
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[].
15
15
16
16
. 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.
18
18
19
19
To get started try one of these suggested prompts.
Copy file name to clipboardExpand all lines: modules/ROOT/pages/af-define-your-agent-network-specification.adoc
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,9 @@ Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites
12
12
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`.
13
13
14
14
[[define-dev-agent]]
15
-
== Define a Network Using MuleSoft Dev Agent
15
+
== Define a Network Using MuleSoft Vibes
16
16
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[].
18
18
19
19
. In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
20
20
. 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.
29
29
[[define-acb-ide]]
30
30
== Define a Network Using Anypoint Code Builder or IDE
31
31
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.
33
33
34
34
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.
35
35
@@ -42,10 +42,10 @@ Use auto-completion menus in Anypoint Code Builder to speed your development. Fo
42
42
43
43
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.
44
44
45
-
=== Add Assets Using MuleSoft Dev Agent
45
+
=== Add Assets Using MuleSoft Vibes
46
46
47
47
. 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.
49
49
50
50
To get started try one of these suggested prompts.
Copy file name to clipboardExpand all lines: modules/ROOT/pages/af-deploy-agent-network-targets.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,12 +44,12 @@ Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites
44
44
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.
45
45
46
46
[[deploy-dev-agent]]
47
-
== Deploy Your Network Using the MuleSoft Dev Agent
47
+
== Deploy Your Network Using MuleSoft Vibes
48
48
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[].
50
50
51
51
. 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.
53
53
54
54
To get started, try one of these suggested prompts.
Copy file name to clipboardExpand all lines: modules/ROOT/pages/af-publish-agent-network-assets.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,12 +13,12 @@ Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites
13
13
If you want to publish your project assets to a different business group, update the relevant `groupId` in `exchange.json`.
14
14
15
15
[[publish-dev-agent]]
16
-
== Publish Your Network Using MuleSoft Dev Agent
16
+
== Publish Your Network Using MuleSoft Vibes
17
17
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[].
19
19
20
20
. 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.
22
22
23
23
To get started try one of these suggested prompts.
= Developing Integrations Using MuleSoft Dev Agent
1
+
= Developing Integrations Using MuleSoft Vibes
2
2
:page-deployment-options: cloud-ide, desktop-ide
3
3
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:
5
5
6
6
* Developing API specifications
7
7
* Creating and configuring applications
@@ -10,7 +10,7 @@ To develop, manage, or maintain your applications, use MuleSoft Dev Agent in Any
10
10
11
11
All of these actions are driven by natural language prompts.
12
12
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:
14
14
15
15
* Flows
16
16
* Connector configurations
@@ -19,7 +19,7 @@ When you generate an integration, MuleSoft Dev Agent transforms your business lo
19
19
20
20
These capabilities are powered by large language models (LLMs) that run within the Salesforce Shared Trust Boundary.
21
21
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.
23
23
24
24
[[before-you-begin]]
25
25
== Before You Begin
@@ -28,33 +28,33 @@ Before you start creating your API spec, make sure you meet the following prereq
28
28
29
29
* xref:start-acb.adoc[Set up and access the web or desktop IDE].
30
30
* 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:
32
32
** *Mule Developer Generative AI User*
33
33
* Make sure Einstein is enabled in Access Management. For more information, see xref:access-management::enabling-einstein.adoc[Enabling Einstein for Anypoint Platform].
34
34
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.
36
36
37
-
== Unified Dev Agent Experience
37
+
== Unified MuleSoft Vibes Experience
38
38
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.
40
40
41
-
Depending on your settings, Dev Agent can:
41
+
Depending on your settings, MuleSoft Vibes can:
42
42
43
43
* 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.
45
45
46
46
For details on configuring permissions and server connections, see xref:troubleshoot-generative-ai.adoc[].
47
47
48
48
== Provide Additional Context
49
49
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:
52
52
53
53
* **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.
55
55
* **Terminal Input** – Share terminal outputs as context for the request.
56
56
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.
58
58
59
59
== Trust Layer
60
60
@@ -63,7 +63,7 @@ The Einstein trust layer bridges Anypoint Platform and the LLMs, as shown in thi
63
63
image::acb-einstein-trust-layer.png["Flow depicting how the trust layer works, including the steps of the flow"]
64
64
65
65
[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.
67
67
. To minimize inaccurate responses, messages are grounded with MuleSoft proprietary data and user context.
68
68
. To ensure safe data transfer to external LLMs, the message is sent via a secure gateway.
69
69
. All data remains within Salesforce-managed boundaries.
@@ -76,5 +76,5 @@ This feature uses AI models that can produce inaccurate or harmful responses. Re
76
76
77
77
== See Also
78
78
79
-
* xref:troubleshooting.adoc[Troubleshooting Dev Agent]
80
-
* xref:api-ai-create-spec.adoc[Creating API Specs with Dev Agent]
0 commit comments