MPS 2026.2 release candidate adds Linux ARM64 builds, including standalone RCPs
JetBrains' MPS 2026.2 release candidate adds Linux ARM64 support, with a matching bundled JetBrains Java Runtime and standalone RCP builds. Teams that package MPS-based tools can test ARM64 distributions before the final release.
The Engineer · Build desk

Map of five parts of MPS packaging. MPS runs on Linux ARM64 with a bundled JetBrains Java Runtime. Standalone RCPs can be built for Linux ARM64. The Build Script Wizard adds a Linux ARM64 distribution. macOS archives move from .zip to .tar.gz. TAR imports keep symbolic links and file permissions.
- capability MPS on Linux ARM64 MPS now runs on Linux ARM64 (AArch64) with a matching bundled JetBrains Java Runtime, claim 2
- capability Standalone MPS-based apps (RCPs) Can now be built for Linux ARM64, claim 3
- decision Build Script Wizard Generated build scripts include a Linux ARM64 distribution alongside the existing platforms, claim 4
- decision macOS archive distributions Switch from .zip to .tar.gz to preserve symbolic links; the wizard does the same for standalone macOS apps, claim 9
- capability Platform plugins, native libraries Imported into a TAR layout, they keep symbolic links and file permissions, so links are not duplicate copies, claim 7
| Who | How | Kind | Claim |
|---|---|---|---|
| MPS on Linux ARM64 | MPS now runs on Linux ARM64 (AArch64) with a matching bundled JetBrains Java Runtime | capability | 2 |
| Standalone MPS-based apps (RCPs) | Can now be built for Linux ARM64 | capability | 3 |
| Build Script Wizard | Generated build scripts include a Linux ARM64 distribution alongside the existing platforms | decision | 4 |
| macOS archive distributions | Switch from .zip to .tar.gz to preserve symbolic links; the wizard does the same for standalone macOS apps | decision | 9 |
| Platform plugins, native libraries | Imported into a TAR layout, they keep symbolic links and file permissions, so links are not duplicate copies | capability | 7 |
What happened
- Build Language gains import files from tar and files from tar entries that read plain TAR, gzip and bzip2 archives.
- Importing into a TAR layout preserves symbolic links and file permissions, so linked native libraries are not copied in twice.
- macOS archive distributions switch from .zip to .tar.gz so that symbolic links survive packaging.
Why it matters
- decision Teams shipping MPS-based RCPs can add a Linux ARM64 target by regenerating build scripts, then choose between testing on the RC or waiting for the final build.
- cost Release scripts that expect a macOS .zip need editing before they meet this build. The work falls on whoever owns packaging and download automation.
- capability Plugins and native libraries distributed as TAR archives can be pulled into a layout with links and permissions intact, which matters for per-platform packaging.
Start with the build script. Regenerating it in the Build Script Wizard adds a Linux ARM64 distribution next to the existing platform distributions [4]. That is the shortest route to an ARM64 artifact you can test.
The post says MPS itself ships with a matching bundled JetBrains Java Runtime [2]. It does not say whether standalone RCPs bundle the same runtime, which bundled plugins carry ARM64 native libraries, or when the final build lands.
The TAR import is where packaging gets easier. The new `import files from tar` and `files from tar` entries read plain TAR, gzip and bzip2 archives [5][6]. The source can be an archive file or another TAR layout defined in the same build script [6]. Into a TAR layout, symbolic links and file permissions are preserved [7].
The old behaviour was the problem. Symbolic links were sometimes replaced with copies of their targets, so large native libraries were included more than once, particularly on macOS [8]. A duplicated native library is the kind of bug that shows up only as a bigger download.
The macOS fix changes a file name. Archive distributions now use .tar.gz instead of .zip, and the wizard generates the same format for standalone macOS applications [9]. JetBrains made the change to preserve symbolic links [9]. In our view, any release script that fetches, names or unpacks the macOS .zip will need an edit before it meets this build. That is the one adoption cost we can see from the post.
The same RC carries a rework of the Projectional Agent Toolkit. JetBrains says that in its measurements with Claude Code and Opus 5 and 5.5, token savings exceeded 50% on common tasks such as DSL modeling or implementing language definitions [11]. That is JetBrains' own workload. The number would transfer to a team whose agents do the same modeling and language-definition work through the MPS MCP API.
Testing now means testing a candidate. JetBrains describes the build as a way to try the release ahead of its official launch [1], and says it improves on the 2026.2 EAP1 build [10].
What to watch
- Whether the Linux ARM64 distribution and wizard output change between this RC and the final 2026.2 build.
- Whether JetBrains documents which bundled plugins ship ARM64 native libraries, and whether standalone RCPs bundle the ARM64 runtime.
- Measurements of the MCP token savings from teams outside JetBrains, on their own DSL and language-definition tasks.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence40
- Adoption
- Insufficient
- Hype gap+10
- Incentives
- Insufficient
- Confidence60
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
JetBrains made a release candidate build of MPS 2026.2 available so users can try out the upcoming release ahead of its official launch.
- [2]
MPS is now available for Linux on ARM64 (AArch64), with a matching bundled JetBrains Java Runtime.
- [3]
Standalone MPS-based applications (RCPs) can be built for Linux ARM64.
- [4]
The Build Script Wizard now includes a Linux ARM64 distribution in its generated build scripts alongside the existing platform distributions.
- [5]
Build Language now supports importing archive contents directly into distribution layouts using the new 'import files from tar' and 'files from tar' entries.
- [6]
Files can be imported from plain TAR archives or archives compressed with gzip or bzip2; the source can be an archive file or another TAR layout defined in the build script.
- [7]
When importing into a TAR layout, symbolic links and file permissions are preserved, which is useful when packaging platform-specific plugins and native libraries because symbolic links remain links instead of duplicate copies of their targets.
- [8]
Previously, symbolic links were sometimes replaced with copies of their targets, causing large native libraries to be included more than once, particularly on macOS.
- [9]
macOS archive distributions now use .tar.gz instead of .zip to preserve symbolic links, and the Build Script Wizard generates the same archive format for standalone macOS applications.
- [10]
Along with numerous bug fixes, the RC brings several key improvements to the previous 2026.2 EAP1 build.
- [11]
In JetBrains' measurements using Claude Code + Opus 5 and 5.5, token savings on common tasks like DSL modeling or implementing language definitions exceeded 50%.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- blog.jetbrains.comMPS 2026.2 Release Candidate Available
1 article · October 15, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- AI Agent ToolingFollow
- Language workbenchesFollow
- Build and packagingFollow
Entities
- JetBrainsFollow
- JetBrains MPSFollow
- Claude CodeFollow