openSUSE's rolling-release distribution is preparing to swap its long-serving YaST installer for the newer Agama tool, a move that will bring the installer stack used across Leap and Tumbleweed into alignment. Phoronix reports that Tumbleweed is now working toward the same transition Leap has already completed, replacing the YaST-based installation flow with Agama.
The change closes a gap rather than opening a new one. Leap migrated to Agama first, leaving Tumbleweed as the last openSUSE distribution still installing through YaST. Once the work lands, both flagship distributions will share a single web-based installer — with a text-mode option alongside it — originally developed by SUSE engineers, ending a period in which openSUSE's two main editions presented users with different installation experiences.
What actually changes at install time
Scope matters here. Only the installer is being replaced. YaST's wider administration toolkit — the system configuration and management modules that remain a hallmark of openSUSE — is not being removed by this transition, and openSUSE has not announced a firm cutover date; the current phase is preparatory.
For a typical Tumbleweed user, the day-to-day difference will mostly be felt at the start of a fresh install. Agama presents a web-based interface, with a text-mode option, rather than the ncurses-and-Qt experience YaST users have known for years. Partitioning, software selection, user creation and bootloader setup will be handled through Agama's workflow instead.
Two practical caveats deserve attention. First, automation: unattended and scripted deployments have historically relied on AutoYaST profiles, and that is the biggest open question in this migration. The source does not establish how Agama's handling of unattended installs compares, so teams with existing AutoYaST estates should confirm Agama's unattended-install support against current documentation before committing — and treat retooling as a project to scope, not a like-for-like swap. Second, edge-case hardware coverage. YaST's installer has accumulated more than two decades of handling awkward scenarios that never appear in clean-VM testing. Agama is younger, and reaching parity on those long-tail cases is the principal rollout risk during the transition.
Enterprise trajectory
The direction of travel is worth noting for readers tracking SUSE's enterprise line. Agama originated inside SUSE, and SLES releases have historically leaned heavily on YaST for installation and administration. openSUSE's shift effectively serves as a proving ground: whatever survives real-world use on Leap and Tumbleweed — automation features, storage edge cases, driver quirks — is the groundwork for any future enterprise adoption. The source makes no mention of an equivalent cutover for SLES, and admins maintaining YaST-based provisioning for SUSE-family systems are not facing an immediate change. Still, the openSUSE project's direction suggests where the ecosystem is heading, which makes this a transition worth watching for anyone running SLES in production.
Why it matters
openSUSE occupies a distinctive niche: a rolling release with a stability reputation and an administration tooling culture built around YaST. Retiring the YaST installer while keeping the rest of YaST is a pragmatic compromise — it gives Tumbleweed a modern, actively developed installer without dismantling the tooling its user base depends on.
For the wider Linux community, the transition is a useful case study in replacing deeply embedded system tooling incrementally. The lack of a hard deadline, and the retention of the broader YaST suite, suggest openSUSE is prioritising continuity over a flag-day rewrite.
Phoronix reports that the work on Tumbleweed is ongoing rather than complete; readers planning installs in the near term should still expect YaST until the project announces otherwise. Specific timelines and the long-term fate of YaST components should be verified against openSUSE's own announcements as the migration progresses.
Source: Phoronix, "openSUSE Tumbleweed Transitioning To Agama Installer."
openSUSE 的滾動更新發行版本正準備把服役多年的 YaST 安裝程式換成較新的 Agama 工具，此舉將使 Leap 與 Tumbleweed 所使用的安裝堆疊趨於一致。Phoronix 報導，Tumbleweed 正朝著 Leap 已完成的同一轉型邁進，以 Agama 取代基於 YaST 的安裝流程。
這項變更是補上缺口，而非開創新局。Leap 先行遷移至 Agama，使 Tumbleweed 成為最後一個仍透過 YaST 進行安裝的 openSUSE 發行版本。待工作完成後，兩個主力版本將共用同一套由 SUSE 工程師開發的網頁式安裝程式——並提供文字模式選項——結束 openSUSE 兩大版本安裝體驗不一的時期。
安裝時實際會有何不同
範圍很重要。被替換的只是安裝程式。YaST 仍廣泛使用的管理工具組——作為 openSUSE 標誌的系統設定與管理模組——並不會因這次轉換而移除，openSUSE 也尚未公布確定的切換日期；目前階段仍屬準備性工作。
對一般 Tumbleweed 用戶而言，日常差異主要出現在全新安裝的開端。Agama 提供網頁式介面（另有文字模式），取代 YaST 用戶多年來熟悉的 ncurses 與 Qt 介面。磁碟分割、軟件選擇、使用者建立與開機載入器設定，日後都將透過 Agama 的流程處理。
有兩點務必留意。第一是自動化：無人值守與腳本化部署歷來依賴 AutoYaST 設定檔，而這正是本次遷移最大的未知數。原始資料並未說明 Agama 對無人值守安裝的處理方式，因此已建置 AutoYaST 環境的團隊，在投入前應先對照最新文件確認 Agama 對無人值守安裝的支援——並把改裝視為需要評估的專案，而非可直接替換的方案。第二是邊緣硬件的覆蓋。YaST 安裝程式二十多年來累積處理了許多在乾淨虛擬機測試中不會出現的棘手情況。Agama 較年輕，在這些長尾情況上達到同等水平，是轉換過程中最大的推出風險。
企業動向
對關注 SUSE 企業產品線的讀者而言，這個方向值得留意。Agama 誕生於 SUSE 內部，而 SLES 版本歷來在安裝與管理方面高度依賴 YaST。openSUSE 的轉變實質上成為一個試驗場：任何在 Leap 與 Tumbleweed 實戰中存活下來的功能——自動化功能、儲存邊緣情況、驅動程式問題——都是日後企業採用的基礎。原始資料並未提及 SLES 有同等的切換計劃，負責 SUSE 家族系統 YaST 部署設定的管理員眼前也不會面對即時變動。不過，openSUSE 專案的方向已顯示整個生態系的走向，因此對於任何在生產環境執行 SLES 的機構來說，這是一次值得觀察的轉換。
為何重要
openSUSE 佔有一個獨特的生態位置：兼具穩定聲譽的滾動版本，以及圍繞 YaST 建立的管理工具文化。退役 YaST 安裝程式、同時保留 YaST 其餘部分，是一項務實的折衷——它讓 Tumbleweed 取得現代化、持續積極開發中的安裝程式，又不拆解用戶所依賴的工具。
對更廣泛的 Linux 社群而言，這次轉換是逐步更換深度嵌入系統工具的有用案例。沒有硬性截止日期，加上保留整套 YaST，顯示 openSUSE 優先考慮連續性，而非一次性重寫。
Phoronix 報導，Tumbleweed 的相關工作仍在進行、尚未完成；近期計劃安裝的用戶，在專案另行通知前仍應預期見到 YaST。具體時間表與 YaST 元件的長期命運，應隨著遷移進展，對照 openSUSE 自身的公告加以查證。
資料來源：Phoronix，〈openSUSE Tumbleweed Transitioning To Agama Installer〉。