You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Include ripgrep in binary builds (windows, win-x64) for offline environments #31734
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
When using OpenCode for Windows (Desktop or EXE) in an offline environment you get the error Transport error get (GET https://github.com/BurntSushi/ripgrep/releases/download/15.1.0/ripgrep-15.1.0-x86_64-pc-windows-msvc.zip)
when opencode tries to use the glob tool.
It would be nice to have ripgrep included in the .exe and in the desktop version if possible.
Reacted by Lijd, Alexander, HAOHANJI, DmitriyKrekshin, Miroshnikov Vladislav and Joda Stößer
Your request (bundling ripgrep in the binary) is a distinct solution, but the underlying problem is the same. If bundling isn't feasible, the error-handling improvement in #21646 may address the user-facing pain in the meantime.
I experienced this exact issue on two Windows machines. On one with internet, everything works - opencode downloads ripgrep into cache on first run. On an air-gapped machine, the cache folder stays empty, and the skill, grep, and glob tools all fail with "ripgrep execution failed". Installing ripgrep manually via winget and placing rg.exe in PATH fixed it, but this should not be required for a Desktop installer.
Workaround that confirms the fix would work: copying a single static rg.exe (~5 MB) to the machine and putting it in PATH resolves everything - no other dependencies needed, no extraction, no cache structure.
Suggestions:
Bundle ripgrep directly in the Windows NSIS installer and macOS DMG (it is a single statically-linked binary, ~5 MB)
Or at minimum, detect that the download failed and print a clear error message telling the user to install ripgrep system-wide, instead of failing silently
I've been looking into this for the Windows CLI case. I have a local prototype that pins official x64/arm64 ripgrep assets, stages them beside opencode.exe, and resolves PATH -> packaged sibling -> cache -> download while preserving the npm and standalone install paths.
Before opening a PR, two questions:
Is the legacy CLI slice the right scope, or should this wait for a unified cross-product decision?
Does the nested rg.exe need to be added to the Azure signing workflow, or should it remain upstream-unsigned?
Activity
github-actions commentedon Jun 10, 2026
This issue might be a duplicate of existing issues. Please check:
Your request (bundling ripgrep in the binary) is a distinct solution, but the underlying problem is the same. If bundling isn't feasible, the error-handling improvement in #21646 may address the user-facing pain in the meantime.
vokasug commentedon Jun 29, 2026
I experienced this exact issue on two Windows machines. On one with internet, everything works - opencode downloads ripgrep into cache on first run. On an air-gapped machine, the cache folder stays empty, and the
skill,grep, andglobtools all fail with "ripgrep execution failed". Installing ripgrep manually via winget and placing rg.exe in PATH fixed it, but this should not be required for a Desktop installer.Workaround that confirms the fix would work: copying a single static rg.exe (~5 MB) to the machine and putting it in PATH resolves everything - no other dependencies needed, no extraction, no cache structure.
Suggestions:
TheMasterFX commentedon Aug 5, 2026
What is the reason it is not build-in yet?
vladislav-miroshnikov commentedon Aug 12, 2026
I've been looking into this for the Windows CLI case. I have a local prototype that pins official x64/arm64 ripgrep assets, stages them beside
opencode.exe, and resolvesPATH -> packaged sibling -> cache -> downloadwhile preserving the npm and standalone install paths.Before opening a PR, two questions:
rg.exeneed to be added to the Azure signing workflow, or should it remain upstream-unsigned?github-actions commentedon Oct 12, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.