no such file or directory, uv_spawn 'C:\Users\user\.local\share\opencode\bin\rg.exe' #2248

Closed
opened 2026-02-16 17:34:50 -05:00 by yindo · 2 comments
Owner

Originally created by @somera on GitHub (Oct 23, 2025).

Description

I see this

Error: ENOENT: no such file or directory, uv_spawn 'C:\Users\user\.local\share\opencode\bin\rg.exe'

But the exe is there. And I'm working with Git Bash on Windows. In this case the folder should be:

/C/Users/user/.local/share/opencode/bin/rg.exe

OpenCode version

0.15.14

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Window 11

Terminal

Git Bash

Originally created by @somera on GitHub (Oct 23, 2025). ### Description I see this ``` Error: ENOENT: no such file or directory, uv_spawn 'C:\Users\user\.local\share\opencode\bin\rg.exe' ``` But the exe is there. And I'm working with Git Bash on Windows. In this case the folder should be: `/C/Users/user/.local/share/opencode/bin/rg.exe` ### OpenCode version 0.15.14 ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System Window 11 ### Terminal Git Bash
yindo added the bug label 2026-02-16 17:34:50 -05:00
yindo closed this issue 2026-02-16 17:34:50 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 23, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #3158: Similar ENOENT error when spawning ripgrep executable, though in a Docker environment rather than Git Bash on Windows

Both issues stem from OpenCode failing to properly locate and execute the ripgrep (rg) binary. While the environments differ, the core problem of executable path resolution appears to be the same.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Oct 23, 2025): This issue might be a duplicate of existing issues. Please check: - #3158: Similar ENOENT error when spawning ripgrep executable, though in a Docker environment rather than Git Bash on Windows Both issues stem from OpenCode failing to properly locate and execute the ripgrep (rg) binary. While the environments differ, the core problem of executable path resolution appears to be the same. Feel free to ignore if none of these address your specific case.
Author
Owner

@rekram1-node commented on GitHub (Oct 23, 2025):

Marking as duplicate of #3158 Ill look into it more

@rekram1-node commented on GitHub (Oct 23, 2025): Marking as duplicate of #3158 Ill look into it more
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2248