←back to thread

177 points Runonthespot | 5 comments | | HN request time: 0s | source
Show context
dang ◴[] No.45161889[source]
[stub for offtopicness]
replies(4): >>45157793 #>>45158731 #>>45158788 #>>45159252 #
ayhanfuat ◴[] No.45157793[source]
Isn't Claude Code's selling point that it doesn't use embeddings?
replies(2): >>45157827 #>>45160582 #
1. joshuanapoli ◴[] No.45157827[source]
I don’t think that “Claude Code” is relevant to this semantic grep tool.
replies(1): >>45157907 #
2. Runonthespot ◴[] No.45157907[source]
bear in mind that Claude Code by default uses grep - if you watch you'll see if it's looking for something it doesn't know the name of, it flails around with different patterns. Try this tool, tell CC to take a look using ck --help and take it for a spin.

CC in my case likes it so much, it started using it to debug the repo rather than grep and suggesting its own additions

replies(2): >>45158011 #>>45158059 #
3. Runonthespot ◴[] No.45158011[source]
Note that it’s grep AND semantic - so Claude can start with a grep strategy and if it finds nothing can switch to semantic, and since it’s local and fast, it keeps in sync easily enough
4. brookst ◴[] No.45158059[source]
How do you tell CC to use it? Just as an entry in Claude.md?
replies(1): >>45158165 #
5. Runonthespot ◴[] No.45158165{3}[source]
To start with just tell it- but yes Claude.md works too.

“We have a new grep semantic hybrid tool installed called ck - check it out using ck --help and take it for a spin”