openSUSE Tumbleweed Moves Toward Agama Installer, Replacing YaST
The rolling-release distribution is preparing to make Agama its default installer before the end of 2026. The change is conditional on testing, and it brings a different approach to package selection, partitioning and automated deployment.
- openSUSE plans to switch Tumbleweed’s default installation experience from YaST to Agama before the end of 2026.
- The cutover depends on successful openQA testing and staging-workflow validation; the date is not guaranteed.
- Agama offers a browser-based interface alongside command-line and API-based installation workflows.
- Users choose from curated software patterns rather than selecting individual packages.
- There is no direct graphical replacement yet for YaST’s Expert Partitioner; advanced layouts remain possible through unattended installation profiles.
- Existing Tumbleweed installations do not need to be reinstalled because of this installer change.
Agama is coming to openSUSE Tumbleweed
The openSUSE Project has announced that its rolling-release distribution, Tumbleweed, is preparing to adopt Agama as its default installer. The project expects the transition to happen before the end of 2026. Agama-based installation images are expected to replace the legacy YaST image as the main download on the official download page in the coming weeks.
However, this is a planned transition rather than a fixed release date. The project says the new images will become the primary downloads only after openQA testing and the staging workflow demonstrate that Agama is sufficiently stable. The announcement also notes that full automated test coverage is still being built.
Agama is not entirely new to the openSUSE ecosystem. It has already been used by openSUSE Leap since Leap 16.0, and Leap 16.1 continues with the installer. Tumbleweed’s move is the next step in the project’s broader adoption.
Why is openSUSE moving away from YaST?
YaST has been a central part of SUSE and openSUSE installation and system administration for decades. The project says YaST is no longer receiving active feature development and is now maintained primarily with minimal changes. At the same time, the software and components around it continue to evolve, making long-term reliance on the older installer increasingly difficult.
Agama takes a more modular approach. It separates the installation interface from the services that configure the system. This makes it possible to drive installation through a web interface, command-line tools or an HTTP API, rather than relying on a single tightly integrated installer interface.
The project also wants a modern installation foundation that can be shared across different SUSE and openSUSE products and support automated deployments.
What changes for users during installation?
1. Browser-based installation interface
Agama presents installation settings through a web-based interface. Users can review localization, networking, storage, software and authentication settings from an overview screen before starting the installation. The installer also provides access to logs and configuration data.
The web interface does not mean the target computer must be administered like a normal desktop browser session. Agama is designed as an installation environment, and its command-line interface offers an alternative for console-driven workflows.
2. Curated software patterns instead of individual packages
One of the most visible differences is software selection. The YaST-based workflow allowed users to select individual packages, while Agama offers a curated list of software patterns. Not every pattern available in the repositories is necessarily exposed by the installer.
A pattern is a predefined collection of packages for a particular role or environment. This approach can make routine desktop and server installations simpler, but it gives users less granular control during the initial installation.
3. Different approach to advanced partitioning
Agama does not currently provide a direct replacement in its graphical interface for YaST’s Expert Partitioner. The openSUSE Agama FAQ explains that the underlying storage capabilities can still be used through unattended installation. A profile can define the desired disk layout and let the installer apply it.
This matters for users who build systems with custom LVM layouts, multiple disks, encryption or other non-standard storage arrangements. Those workflows may require more preparation than selecting options in a graphical partitioning tool.
4. Automation through profiles, CLI and API
Agama supports partially or fully unattended installations. These can be driven by scripts using its command-line interface, JSON-based profiles (using Jsonnet), or external tools that communicate with its HTTP interface. Agama can also process many commonly used AutoYaST profile sections, although not every AutoYaST feature or section is supported.
YaST and Agama: key differences
| Area | YaST-based installer | Agama |
|---|---|---|
| Primary interface | Traditional installer interface | Web-based interface, with CLI and API options |
| Software selection | Individual packages and patterns | Curated software patterns |
| Advanced partitioning | Expert Partitioner available | No direct graphical equivalent yet; use unattended profiles for advanced layouts |
| Automated deployment | AutoYaST workflows | CLI scripts, JSON/Jsonnet profiles and HTTP API; selected AutoYaST profile support |
| Project direction | Primarily maintenance | Modern installer under active development |
What should testers check before the transition?
openSUSE is asking users to test the new installer and report issues before the default download changes. The project specifically wants feedback from less common installation scenarios, where regressions can be harder to detect.
- RAID and LVM storage configurations.
- Systems with multiple physical disks.
- Serial-console installations.
- Offline installation workflows.
- Unusual or less common hardware configurations.
- Profile-based and unattended installations.
The project says the offline installer image includes a pre-filled package cache and can install Tumbleweed without a network connection. A network-based installer image is also available. The existing traditional image remains available during the transition.
How to test the Agama installer
Users can obtain the Tumbleweed Agama images from the official openSUSE download infrastructure. The project announcement links to an offline installer image and a network installer image. Check the official announcement for the current image locations and testing status before downloading.
- Download the Tumbleweed offline installer (x86_64)
- Browse Tumbleweed appliance and network installer images
- Visit the official openSUSE Tumbleweed download page
Because the cutover depends on test results, users should confirm the current status on the official openSUSE site. The traditional YaST-based installer remains available for now.
Does this affect existing Tumbleweed installations?
No reinstall is required simply because Tumbleweed changes its installer. The transition mainly affects how new systems are installed. It also does not mean that all YaST-related packages will immediately disappear from the distribution. The project has been reducing YaST’s role in new installation patterns, but the packages remain available for now.
Users with an existing Tumbleweed system should continue managing updates through the normal Tumbleweed update process. The installer transition is not, by itself, an operating-system migration or a requirement to rebuild an existing machine.
What this means for Linux users and administrators
For everyday desktop users, Agama’s curated software choices and web-based workflow may make installation more straightforward. For administrators, its CLI and API offer useful building blocks for repeatable deployments and integration with automation platforms.
The main trade-off is flexibility at installation time. Users who depend on individual package selection or the YaST Expert Partitioner should test their workflows early and learn the profile-based alternatives. The transition will be most successful if these advanced scenarios receive enough real-world testing before Agama becomes the default.
Final thoughts
Agama represents a significant change in how openSUSE Tumbleweed is installed, but the move is not an overnight removal of YaST from the distribution. The project is taking a staged approach, with automated testing and community feedback determining when the new images become the primary download.
For users, the most important points are the switch to curated software patterns, the different approach to advanced partitioning and the expanded automation options. Testing Agama in a virtual machine now is a sensible way to prepare—especially for administrators with custom storage layouts or unattended deployment workflows.