←back to thread

Show HN: Semantic grep with local embeddings

(github.com)
177 points Runonthespot | 2 comments | 07 Sep 25 11:20 UTC | HN request time: 0s | source
Show context
0x696C6961 ◴[07 Sep 25 14:24 UTC] No.45158402[source]▶
This is cool, but I don't understand why it tries to re-implement (a subset of) grep. Not only that, but the grep-like behaviour is the default and I need to opt-in to the semantic search using the --sem flag. If I want grep I can use grep/ripgrep.
replies(2): >>45158513 #>>45161164 #
1. Runonthespot ◴[07 Sep 25 14:35 UTC] No.45158513[source]▶
Fair comment- the initial thinking was to have both and in fact a hybrid mode too which fuses results so you can get chunks that match both semantically and on keyword search in one resultset. Later could add a reranker too.
replies(1): >>45158910 #
2. alvis ◴[07 Sep 25 15:14 UTC] No.45158910[source]▶
Or another way of thinking. How much is the penalty we are talking about for semantic vs conventional grep?

My thinking is that for large codebase, sorting embedding matches maybe more efficient than reading all files and hence there is no point to put semantic search behind a --semantic flag