Skip to content

[FEATURE]: Include ripgrep in binary builds (windows, win-x64) for offline environments #31734

Closed as not planned

Description

@TheMasterFX

Feature hasn't been suggested before.

  • 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.

Activity

  1. github-actions commented on Jun 10, 2026

    @github-actions
    Contributor

    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.

  2. vokasug commented on Jun 29, 2026

    @vokasug

    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
  3. TheMasterFX commented on Aug 5, 2026

    @TheMasterFX
    Author

    What is the reason it is not build-in yet?

  4. vladislav-miroshnikov commented on Aug 12, 2026

    @vladislav-miroshnikov

    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:

    1. Is the legacy CLI slice the right scope, or should this wait for a unified cross-product decision?
    2. Does the nested rg.exe need to be added to the Azure signing workflow, or should it remain upstream-unsigned?
  5. github-actions commented on Oct 12, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions