Hear from Salesforce leaders on how to create and deploy Agentforce agents.
Contact Us 1-800-596-4880

Command Reference

Anypoint Code Builder provides a set of commands through the Command Palette.

MuleSoft Commands

  • Add an API spec fragment from Exchange to the project directory so that you can include the fragment in your spec. For a procedure that uses this command, see Add a Fragment from Exchange to Your Project.

    MuleSoft: Add Fragment dependency from Exchange
    command
  • Start an API design project. You can also start the project from the UI. See Creating and Importing API Specifications.

    MuleSoft: Design an API
    command
  • Start an integration project. You can also start an integration project from the UI. See Creating Integrations.

    MuleSoft: Develop an Integration
    command
  • Download a supported version of Mule runtime engine and Java from Anypoint Code Builder. See also, Version Settings for Mule, Java, and Connectors.

    MuleSoft: Download Mule Runtime and Java Versions
    command
  • Export a shareable JAR file that contains an integration or implementation project. Both types of projects are Mule applications. See Export to a Shareable JAR File.

    MuleSoft: Export Mule Application Sources
    command
  • Export a Mule project with its compiled code and all dependencies into a JAR file that you can deploy. See Export to a Deployable JAR File.

    MuleSoft: Export Project to Mule Deployable Jar
    command
  • Export a compressed file that contains your project’s workspace folders, logs, and information about environment variables, CPU, operating system, and system properties. See Export Troubleshooting Information.

    MuleSoft: Export Troubleshooting Information
    command
  • Open the Settings page for Anypoint Code Builder settings, which include settings for the Anypoint Platform host (EU or US). For an example that uses the command, see Set the Desktop IDE to the EU or US Cloud.

    MuleSoft: Open ACB Settings
    command
  • Publish an API spec or fragment from the IDE to Anypoint Exchange. See Publish an API spec to Exchange.

    MuleSoft: Publish API Specification to Exchange
    command
  • After scaffolding an API design project from the IDE into an interface within an implementation project and making subsequent changes to the design project, use this command from the design project to re-scaffold your changes into your interface. See Re-Scaffold the API Spec.

    MuleSoft: Re-scaffold this local API
    command
  • Validate your API specification against rules in all rulesets added to a design project. For information about rulesets, see Validating API Specifications Against Governance Rulesets.

    MuleSoft: Run Governance Validation with all Rulesets and Rules
    command
  • Search for an asset by its name in Anypoint Exchange.

    MuleSoft: Search in exchange
    command
  • Open the Welcome tab for Anypoint Code Builder. See an example of the tab in Discovering the UI.

    MuleSoft: Show Welcome
    command

Other Commands

Other helpful commands include the following:

  • Open a project folder from the Command Palette. For examples that use this command, see Adding Folders to Your Home Directory.

    File: Open Folder
    command
  • Open the Anypoint Code Builder panel from the IDE. The panel provides links to Quick Actions, Documentation, and other items. See an example of the panel in Discovering the UI.

    View: Show Anypoint Code Builder
    command