WASM ripgrep SIMD requirement breaks @ file fuzzy search on CPUs without AVX2 support

[ssizzz]

What happened

After upgrading opencode from v1.4.3 to v1.4.6, the @ file search stopped working entirely. Running opencode debug rg files gives a WASM error.

Error message

WebAssembly.Module doesn't parse at byte 175: wasm-simd is not enabled, in function at index 81

My environment

• opencode v1.4.6 (also tried the baseline package variant, same error)
• CPU flags show sse4_1 sse4_2 ssse3 but no AVX2
• System ripgrep is installed and works fine (rg --version returns 14.1.1)

Steps to reproduce

1. Run opencode on a CPU without AVX2 support (check with cat /proc/cpuinfo | grep avx2)
2. Try @ file search in TUI or run opencode debug rg files --limit 5
3. See WASM SIMD error

Workaround

Back to v1.4.3

The older version appears to use external ripgrep instead of WASM, which works on my system.

[github-actions]

Thanks for updating the issue! It now follows our contributing guidelines — the description is clear, concise, and includes the error message, environment details, and steps to reproduce. We appreciate you taking the time to revise it.

[thdxr]

wait why did you close it?

[niklas88]

I get the same issue with opencode 1.4.7 running on my NAS which sadly only has an Intel N5105. This definitely worked fine in v1.4.3 and makes opencode unusable on older CPUs.

[qaqland]

1.4.19 works well