anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

ripgrep causes Grep tool to fail in the presence of broken symlinks #5478

New Issue
Closed
opened 2026-02-16 17:53:10 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:53:10 -05:00
Owner
Copy Link
Copy Source

Originally created by @andrewphelpsj on GitHub (Jan 13, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

When a model calls the Grep tool, it will fail if the target directory, or any child of that directory, contains broken symlinks. This is directly caused by using the ripgrep --follow parameter (https://github.com/anomalyco/opencode/pull/7501).

Here is an example of what ripgrep is returning in this case:

[phelps@arch opencode]$ rg --follow Ripgrep.search
rg: ./subdir/broken: No such file or directory (os error 2)
packages/opencode/src/cli/cmd/debug/ripgrep.ts
79:    const results = await Ripgrep.search({

packages/opencode/src/server/server.ts
1937:            const result = await Ripgrep.search({
[phelps@arch opencode]$ echo $?
2

And opencode shows this as:

✱ Grep "GrepTool" in .
Error: ripgrep failed: rg: /home/phelps/opencode/subdir/broken: No such file or directory (os error 2)

Note the exit code of 2. This causes the Grep tool to return an error, and none of the content. It might make sense to only return an error if there isn't anything in stdout? However, then you'd end up stripping some potentially useful information that ripgrep could be reporting.

Here is the relevant section of the ripgrep man page:

•  2 exit status occurs when an error occurred. This is true for both
   catastrophic errors (e.g., a regex syntax error) and for soft
   errors (e.g., unable to read a file).

Plugins

No response

OpenCode version

1.1.18

Steps to reproduce

Create a broken symlink somewhere in your project and ask a model to grep for something in the root of the repo:

phelps@arch ~/opencode> mkdir subdir
phelps@arch ~/opencode> ln -s ../broken subdir/

Screenshot and/or share link

Short exchange where this resulted in an extra turn in which rg was invoked manually: https://opncd.ai/share/6djY8XRM

Operating System

Arch Linux

Terminal

foot

Originally created by @andrewphelpsj on GitHub (Jan 13, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description When a model calls the Grep tool, it will fail if the target directory, or any child of that directory, contains broken symlinks. This is directly caused by using the `ripgrep --follow` parameter (https://github.com/anomalyco/opencode/pull/7501). Here is an example of what ripgrep is returning in this case: ``` [phelps@arch opencode]$ rg --follow Ripgrep.search rg: ./subdir/broken: No such file or directory (os error 2) packages/opencode/src/cli/cmd/debug/ripgrep.ts 79: const results = await Ripgrep.search({ packages/opencode/src/server/server.ts 1937: const result = await Ripgrep.search({ [phelps@arch opencode]$ echo $? 2 ``` And opencode shows this as: ``` ✱ Grep "GrepTool" in . Error: ripgrep failed: rg: /home/phelps/opencode/subdir/broken: No such file or directory (os error 2) ``` Note the exit code of 2. This causes the Grep tool to return an error, and none of the content. It might make sense to only return an error if there isn't anything in stdout? However, then you'd end up stripping some potentially useful information that `ripgrep` could be reporting. Here is the relevant section of the ripgrep man page: ``` • 2 exit status occurs when an error occurred. This is true for both catastrophic errors (e.g., a regex syntax error) and for soft errors (e.g., unable to read a file). ``` ### Plugins _No response_ ### OpenCode version 1.1.18 ### Steps to reproduce Create a broken symlink somewhere in your project and ask a model to grep for something in the root of the repo: ``` phelps@arch ~/opencode> mkdir subdir phelps@arch ~/opencode> ln -s ../broken subdir/ ``` ### Screenshot and/or share link Short exchange where this resulted in an extra turn in which `rg` was invoked manually: https://opncd.ai/share/6djY8XRM ### Operating System Arch Linux ### Terminal foot
yindo added the bug label 2026-02-16 17:53:10 -05:00
yindo closed this issue 2026-02-16 17:53:10 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#5478
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?