Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Skip incompatible Bun-based agents on CPUs below their instruction-set requirements
Reported by t0d0r · filed Aug 23, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
- Omarchy: 4.0.0-1
- Hardware: Apple iMac10,1
- CPU: Intel Core 2 Duo E7600 (Penryn, x86-64-v1)
- CPU features: SSE4.1; no SSE4.2, POPCNT, AVX, or AVX2
- Kernel: 7.1.8-arch1-3
- mise: 2026.8.6-1
What's wrong?
Omarchy's default user installation script installs Claude and Pi unconditionally:
/usr/share/omarchy/install/user/mise.sh
omarchy-mise-install claude
# ...
omarchy-mise-install piThe current native executables for both tools are Bun-based and require CPU
instructions unavailable on older x86-64 hardware.
On this machine, both agents install successfully but crash with SIGILL when
launched.
Pi 0.84.2:
Process: /home/todor/.local/share/mise/installs/pi/0.84.2/pi/pi
Signal: SIGILL (ILL_ILLOPN)
Kernel: trap invalid opcode at pi+0x37fc488Claude 2.1.241 crashed repeatedly at the same address:
Process: /home/todor/.local/share/mise/installs/claude/2.1.241/claude
Signal: SIGILL
Kernel: trap invalid opcode at claude+0x198e3b3There was no memory pressure or OOM event. Approximately 9.2 GiB was available
and swap was unused.
This CPU has SSE4.1 but lacks SSE4.2, POPCNT, AVX, and AVX2. Existing upstream
reports confirm that current Bun-compiled Claude binaries fail on CPUs below
their instruction baseline. Pi's release build script likewise compiles the
standalone executable using Bun's regular bun-linux-x64 target.
Steps to reproduce
- Install Omarchy 4.0.0 on an x86-64-v1 CPU lacking SSE4.2/POPCNT/AVX.
- Allow the default user installation to install Claude and Pi through mise.
- Run
claudeorpi. - Observe an immediate or early SIGILL/core dump.
Expected behavior
Omarchy should detect CPU capabilities before installing known incompatible
native agents.
Possible behavior:
- Skip incompatible tools and print a clear explanation.
- Offer a compatible Node-based installation where one exists.
- At minimum, warn that the installed executable cannot run on this CPU.
A feature-based check is preferable to checking CPU model names. The required
feature set should ideally be recorded per affected tool because upstream binary
requirements may differ or change.
Actual behavior
The agents install normally and only reveal the incompatibility by repeatedly
crashing and generating systemd core dumps.
Diagnostic summary
omarchy debug --no-sudo --print identifies the CPU as:
Intel Core2 Duo E7600
Architecture level: x86-64-v1
Flags: sse sse2 sse3 ssse3 sse4_1The journal contains repeated Claude SIGILL dumps and one Pi SIGILL dump.
Filed by GPT-5 via Codex.
View raw text
### System details - Omarchy: 4.0.0-1 - Hardware: Apple iMac10,1 - CPU: Intel Core 2 Duo E7600 (Penryn, x86-64-v1) - CPU features: SSE4.1; no SSE4.2, POPCNT, AVX, or AVX2 - Kernel: 7.1.8-arch1-3 - mise: 2026.8.6-1 ### What's wrong? Omarchy's default user installation script installs Claude and Pi unconditionally: `/usr/share/omarchy/install/user/mise.sh` ```bash omarchy-mise-install claude # ... omarchy-mise-install pi ``` The current native executables for both tools are Bun-based and require CPU instructions unavailable on older x86-64 hardware. On this machine, both agents install successfully but crash with SIGILL when launched. Pi 0.84.2: ```text Process: /home/todor/.local/share/mise/installs/pi/0.84.2/pi/pi Signal: SIGILL (ILL_ILLOPN) Kernel: trap invalid opcode at pi+0x37fc488 ``` Claude 2.1.241 crashed repeatedly at the same address: ```text Process: /home/todor/.local/share/mise/installs/claude/2.1.241/claude Signal: SIGILL Kernel: trap invalid opcode at claude+0x198e3b3 ``` There was no memory pressure or OOM event. Approximately 9.2 GiB was available and swap was unused. This CPU has SSE4.1 but lacks SSE4.2, POPCNT, AVX, and AVX2. Existing upstream reports confirm that current Bun-compiled Claude binaries fail on CPUs below their instruction baseline. Pi's release build script likewise compiles the standalone executable using Bun's regular `bun-linux-x64` target. ### Steps to reproduce 1. Install Omarchy 4.0.0 on an x86-64-v1 CPU lacking SSE4.2/POPCNT/AVX. 2. Allow the default user installation to install Claude and Pi through mise. 3. Run `claude` or `pi`. 4. Observe an immediate or early SIGILL/core dump. ### Expected behavior Omarchy should detect CPU capabilities before installing known incompatible native agents. Possible behavior: - Skip incompatible tools and print a clear explanation. - Offer a compatible Node-based installation where one exists. - At minimum, warn that the installed executable cannot run on this CPU. A feature-based check is preferable to checking CPU model names. The required feature set should ideally be recorded per affected tool because upstream binary requirements may differ or change. ### Actual behavior The agents install normally and only reveal the incompatibility by repeatedly crashing and generating systemd core dumps. ### Diagnostic summary `omarchy debug --no-sudo --print` identifies the CPU as: ```text Intel Core2 Duo E7600 Architecture level: x86-64-v1 Flags: sse sse2 sse3 ssse3 sse4_1 ``` The journal contains repeated Claude SIGILL dumps and one Pi SIGILL dump. Filed by GPT-5 via Codex.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
- Fixed bypr/11514· confirmed
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 08:28 UTC