Anypoint Code Builder relies on Visual Studio Code (VS Code), Java, Node.js, Maven, and local build artifacts. To avoid timeouts, slow dependency resolution, and poor responsiveness, your environment must meet the following minimum specifications. Recommended values improve performance for larger workspaces and frequent local runs.
For supported operating systems and extension compatibility, see Anypoint Code Builder Release Notes.
To check whether your machine meets these specifications and apply available optimizations automatically, ask MuleSoft Vibes or Claude Code to run the run-system-diagnostics skill.
Hardware Requirements
| Component | Minimum | Recommended |
|---|---|---|
CPU |
8 cores or 8 vCPUs |
More cores for parallel builds and multiple large projects |
RAM |
32 GB |
Additional memory for multiple VS Code windows and heavy local testing |
Primary storage type |
NVMe SSD (PCIe 3.0 or higher) |
Same; avoid network-only or heavily virtualized disks for the OS, user profile, and project roots |
Free disk space |
50 GB |
100 GB |
Network |
1 Gbps |
10 Gbps (for large dependency downloads and corporate artifact repositories) |
Storage Performance
Local disks that can’t sustain the following metrics often show slow indexing, Maven repository access, and Mule application startup.
Confirm values with your storage vendor or disk benchmark tooling on the volume that hosts your user profile, local Maven repository, VS Code data, and project directories. Consider input/output operations per second (IOPS) as well; higher IOPS generally improve responsiveness for random small-file access.
| Metric | Minimum Requirement |
|---|---|
Random read IOPS (4 KB) |
10,000 IOPS |
Random write IOPS (4 KB) |
8,000 IOPS |
Sequential read |
1,250 MB/s |
Sequential write |
1,000 MB/s |
Antivirus, endpoint detection, and real-time scanning can reduce read and write speeds below these minimums. To reduce this impact, configure antivirus and endpoint protection exclusions.
Configure Antivirus and Endpoint Protection Exclusions
On managed devices, add exclusions for the processes and directories that Anypoint Code Builder and its toolchain use most intensively. Exclusions reduce file locking, false positives, and severe I/O latency during builds. Your organization’s security policy decides whether exclusions are allowed, so use the list with your security team.
For the full list of processes and directories to exclude, see Antivirus Exclusion Paths.
Windows Performance
On Windows, avoid running projects from network-mapped drives, because remote file access adds latency to project loading and canvas responsiveness. Store projects on local storage that meets the requirements in Storage Performance, and keep Anypoint Extension Pack updated to the latest version to benefit from ongoing file read and write optimizations for Windows.
Power Settings
Power management can throttle CPU and disk performance during long builds or local runs.
-
Windows: Prefer a High performance or Balanced power plan while you work; avoid battery saver or aggressive power saving when the machine is on AC power.
-
macOS: On notebooks, reduce battery-focused throttling where your org allows it—for example, adjust System Settings under Battery or Energy when plugged in.