Viewing profile — shrishdwi

that's just when our claude limit's were about to exhaust :/ as we have to spin up a whole claude session to test it. but you could 100% be Sherlock Holmes!

[flagged]

Feedback taken, actually as we have been iterating on this everyday, the README got updated by the coding agents in this process.

we are running them on a recurring basis, so will keep on updating that 50 number. and hence as it's currently running that section gets updated by claude only.

LSP is for when you already know the symbol and want an exact answer, like go-to-definition or find-references. graft is for the step before that: you ask "where does auth happen" …

We made this for X audience initially but got a lot of praise for it on reddit, so decided to put in the README. Sorry it made it more difficult for you.

In our tests, graft found the right code about twice as often as graphify (MRR 0.73 vs 0.38, recall@10 54% vs 20%). The difference is simple: graft searches inside the actual code,…

for your point #2: people are trying out to give coding agents LSP support, not sure though how well it'll work but it gives coding agents a better idea of the language in which th…

We are using hooks to direct the coding agent to use graft grep instead of just grep, so this should ideally not happen. Also, for java projects we do support a more deeper graph, …

For the staleness specifically we are using hooks on claude code and codex, where on every turn, or post edit or pre-tool use, we sync the graph. so that graph never goes stale. We…

if the changes are on your local when you pull those changes from the remote, graft will be auto-synced before graft tool use.

Opus 5 is very paranoid on giving proofs for every thing it claimed. so I let it keep this one line.

we use claude hooks. so that, post edits it auto updates and before using the graft tools also we check if it's already in sync. Hooks also solve for the issue of the LLMs not call…

Thanks for sharing!