[fix] Enable accelerated Alacritty on macOS 26+ - #176
Open
Fail-Safe wants to merge 4 commits into
Open
Conversation
Fail-Safe
marked this pull request as ready for review
September 10, 2026 21:12
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enable accelerated Alacritty on Apple Silicon Macs running macOS 26 or newer with the released VirGL fix. Normal Alacritty launches use the packaged binary instead of the factory software-rendering wrapper.
Platform requirement
This raises Try Omarchy's minimum macOS version to 26.0. The published VirGL v1.0.42 bottle requires macOS 26.0. The app metadata, Swift deployment target, build and launcher checks, compatibility verification, CI runner, and documentation now agree on that requirement. Apple Silicon remains required.
Acceptance of this higher OS minimum is part of review. Runtime testing below was performed on macOS 27; it does not establish a completed macOS 26 host test.
Changes
Required before merge
Validation
GitHub CI on macOS 26 passed for commit
c7be078b2fa6fd8ae16ef1db3047d041674a8da3(2m55s). The final full local suite passed, including 242 Swift tests and 119 guest tests, plus the shutdown-race regression, isolated launcher contracts, and storage checks. A clean QEMU runtime source build and a fresh containerized guest build passed. The complete app built successfully; code-signature verification passed, and compatibility verification checked all 17 bundled Mach-O images against macOS 26.0. The migration helper is included as an executable app resource.The final packaged app booted a fresh factory guest, first-boot setup completed, and the remaining interaction checks passed. The technical checklist is complete; maintainer review still needs to accept the macOS 26 minimum.
Released-package runtime evidence
The v1.0.42 archive matched SHA-256
64c37340757cf300712d8e74dc43759f81058ec58cf424094d5f79c9c82c0984. An isolated app using that driver with ANGLE 1.0.16 and libepoxy 1.0.5 booted a disposable guest on macOS 27.Final packaged-app validation used the fresh guest with kernel 7.2.4-1. Omarchy's terminal installer selected
Alacritty.desktop; its normal launcher started/usr/bin/alacrittywithoutLIBGL_ALWAYS_SOFTWARE. Visible ASCII, colored text, accented Latin, and Greek output were confirmed. Three additional launches each reportedRunning on virglandUsing dual source blending.TERMINAL PASTE: PASS. Original host clipboard contents were restored./usr/bin/alacrittyresolution.The CJK probe showed missing-glyph boxes, so these results do not claim CJK font coverage. Runtime testing was on macOS 27; hosted build/test CI passed on macOS 26.
Earlier controlled tests of the equivalent fix on the previously pinned driver measured about 32% lower guest process CPU with essentially unchanged elapsed time. That is older-version, workload-specific evidence, not a v1.0.42 benchmark or a general FPS/battery-life claim. Kitty's separate OpenGL workaround and the pre-existing combined MRT transition failure remain outside this change.