Hey, thanks for the detailed report. I can see the issue. Rules discovery really does hardcode --follow in the ripgrep calls, and the search.followSymlinks setting doesn’t affect it.
I shared this with the team, along with the details from your report.
As a workaround for now, you can use a wrapper around the rg binary on the remote machine. A user in a similar thread suggested this approach:
#!/bin/bash
DIR=$(find ~/.cursor-server/ -name "rg" -type f | xargs dirname)
mv "$DIR/rg" "$DIR/rg.orig"
cat > "$DIR/rg" <<'EOF'
#!/bin/bash
# Strip --follow from arguments
args=()
for arg in "$@"; do
[[ "$arg" != "--follow" ]] && args+=("$arg")
done
exec "$(dirname "$0")/rg.orig" "${args[@]}"
EOF
chmod +x "$DIR/rg"
After that, restart cursor-server (pkill -f '\.cursor-server/.*node') and reconnect.
Downside is that after a Cursor update, the binary will get overwritten and you’ll need to redo this. But for now, this is the only way to work around the issue.
Let me know if it helps.