Contact Us 1-800-596-4880
  1. Homepage
  2. Anypoint Code Builder

  3. MuleSoft Dev Agent Overview

MuleSoft Dev Agent Overview

MuleSoft Dev Agent is now MuleSoft Vibes. You may see references to MuleSoft Dev Agent in our application and documentation.

MuleSoft Dev Agent is a purpose-built assistant for the development lifecycle, available directly in Anypoint Code Builder.

MuleSoft Dev Agent enables you to build, deploy, and manage your projects using natural language prompts.

Dev Agent integrates with the MuleSoft MCP Server, which provides a set of agentic tools that connect Dev Agent directly to your MuleSoft environment. Through this integration, Dev Agent can perform actions and retrieve data on your behalf, enabling capabilities such as:

  • Developing API specifications

  • Creating and configuring applications

  • Creating agent networks

  • Searching for assets

  • Deploying and managing instances

  • Securing your applications

These features are powered by large language models (LLMs) that operate within the Salesforce Shared Trust Boundary.

MuleSoft Dev Agent is part of the broader MuleSoft AI ecosystem, which also includes capabilities such as Map with AI and Map and Transform with AI. For an overview of all MuleSoft AI features, see the Learning Map: MuleSoft AI.

MuleSoft Dev Agent is available on US, EU, Canada, and Japan cloud hosts.

Before You Begin

Before using MuleSoft Dev Agent, make sure that you meet these prerequisites:

Authentication happens through the user logged in to Anypoint Code Builder. MuleSoft Dev Agent inherits the same permissions as that user and can only execute actions that the user is authorized to perform in Anypoint Platform.

Use MuleSoft Dev Agent

You can open MuleSoft Dev Agent from the:

  • Toolbar icon

  • Top navigation bar

  • Build with AI card in the project canvas

When you submit a prompt, MuleSoft Dev Agent processes it using the MuleSoft MCP Server and performs actions such as generating API specifications or integration flows.

Depending on your configuration, MuleSoft Dev Agent can:

  • Request approval before writing to your files

  • Write automatically if Auto-approve is enabled in settings

Plan and Act Modes

MuleSoft Dev Agent operates in two modes:

  • Plan Mode Dev Agent analyzes your prompt and produces a step-by-step plan describing how it will accomplish the task. No actions are executed automatically in this mode.

  • Act Mode Dev Agent attempts to perform the actions outlined in the plan by using the MuleSoft MCP Server tools to modify files, create resources, or execute changes to your project.

You can switch between modes depending on whether you prefer to review the plan before execution or allow Dev Agent to act directly.

How Dev Agent Generates Code

MuleSoft Dev Agent uses MuleSoft-optimized AI pipelines to generate high-quality code for API specifications and integration flows.

The pipelines are exposed to Dev Agent through these MCP tools:

  • generate_mule_flow – Generates Mule integration flows.

  • generate_api_spec – Generates API specifications from natural language prompts.

Because these tools run on pipelines optimized specifically for MuleSoft use cases, users typically receive higher-quality code outputs (on average, 60% better) compared to generic generation.

To ensure the best results:

  • Verify that the MuleSoft MCP Server is loaded in Dev Agent prior to sending a prompt.

  • Make sure Dev Agent is invoking these specialized tools.

  • Verify that all required prerequisites for Dev Agent and MCP Server are enabled in your environment.

For more information about how MuleSoft’s AI generation pipelines work, see the MuleSoft research blog.

Use Checkpoints to Track Changes

When you have a folder or directory open in Visual Studio Code, you can use checkpoints to track changes to your workspace.

Checkpoints capture the state of your files and Dev Agent tasks at a specific moment in time, allowing you to restore or compare your project with a prior state.

To restore or compare your workspace:

  1. Open a folder or directory in Visual Studio Code.

  2. Interact with Dev Agent to generate actions that create checkpoints.

  3. In the MuleSoft Dev Agent panel, locate the checkpoint that you want to reference.

  4. Choose one of the available options:

    • Restore – Revert your workspace to the selected checkpoint. You can restore:

      • Restore Files Only – Restores only the file changes in your workspace.

      • Restore Task Only – Restores only the task history associated with the checkpoint.

      • Restore Files and Tasks – Restores both the file changes and the task history.

    • Compare – Compare the current state of your workspace to the selected checkpoint. This opens a comparison view that highlights the differences between your current files and the files at the time the checkpoint was created.

Add Workflows and Rules

Rules and Workflows allow developers to customize how MuleSoft Dev Agent operates within their project.

Rules Define natural-language constraints or guidelines for how Dev Agent should generate content. You can use rules to enforce naming conventions, ensure consistent error handling, or maintain coding standards across your workspace. Rules can be defined at two levels: * Global – Applies to all prompts sent to Dev Agent. * Workspace – Applies only to the active workspace.

Workflows create predefined multi-step tasks that Dev Agent executes automatically. Workflows let you streamline repeated development steps and can be triggered using slash commands (for example, /workflow-name) in the Dev Agent panel.

Add rules or workflows

  1. Open MuleSoft Dev Agent in the sidebar.

  2. Select Settings.

  3. In the Rules and Workflows section, choose whether you want to add a rule or a workflow.

  4. Select Add Rule or Add Workflow.

  5. Provide the required information:

    • For rules, enter the natural-language instruction you want Dev Agent to follow.

    • For workflows, enter a name, an optional description, and the steps the workflow should run.

  6. Select Save.

You can edit or delete existing rules and workflows from the same section.

Provide Dev Agent with Context

You can improve the accuracy of MuleSoft Dev Agent’s output by providing additional context files or inputs. Examples include requirement files (requirements.txt), configuration folders, logs, URLs, or terminal output.

To add context:

  1. In the MuleSoft Dev Agent panel, click the Add Context icon in the lower-left corner.

  2. Select files or folders to attach, paste the input or output from terminal, or paste a URL.

  3. Confirm to add the context to your current task.

You can also add context directly from the prompt input box by typing @, which opens the same context selector.

These inputs are used as contextual references during generation.

Add Commands

Commands provide quick shortcuts for interacting with MuleSoft Dev Agent. You can invoke any command by typing / in the prompt input box.

Dev Agent includes several built-in commands:

  • /newrule — Create a new rule based on the current conversation.

  • /newchat — Start a new chat that carries over context from your current task.

  • /reportbug — Report an issue by creating a GitHub ticket with Agentforce Vibes formatting.

Workflows that you define also appear as commands under Workflow Commands. You can trigger them the same way by typing / followed by the workflow name.

Configure MuleSoft Dev Agent Settings

You can customize how MuleSoft Dev Agent interacts with your project through the Settings panel. To access this panel, click the Auto-approve section at the bottom of the MuleSoft Dev Agent window.

The available options include:

  • Auto-approve: Automatically apply changes without prompting for confirmation.

  • Read project files: Allow MuleSoft Dev Agent to read project files for context.

  • Edit project files: Allow MuleSoft Dev Agent to write changes directly to your project.

  • Read all files: Allow MuleSoft Dev Agent to read all files on your computer.

  • Edit all files: Allow MuleSoft Dev Agent to edit any file on your computer.

  • Use MCP Servers: Allow MuleSoft Dev Agent to use connected MCP servers.

  • Execute safe commands: Allow MuleSoft Dev Agent to execute safe terminal commands.

  • Execute all commands: Allow MuleSoft Dev Agent to execute any terminal command.

  • Use the browser: Allow MuleSoft Dev Agent to launch and interact with websites in a browser.

View Conversation History

MuleSoft Dev Agent allows you to return to tasks you have previously started and continue working from where you left off.

To open a recently started task:

  1. In the MuleSoft Dev Agent panel, locate the Recent Tasks section.

  2. Select the task you want to reopen.

If the task is not listed under Recent Tasks:

  1. Click View All History.

  2. Use the search bar to find a specific task, or browse your full history list.

You can sort tasks by:

  • Newest

  • Oldest

  • Most Tokens

  • Other available criteria

You can also filter tasks by:

  • Workspace

  • Favorites

To favorite a task, click the Star icon next to the task entry.

Delete History

You can remove past tasks in two ways:

  • Delete specific tasks – Deletes the specific tasks you select.

  • Delete all history – Clears all tasks.

See Also