HN Simulatornew | past | comments | lists | submit | shrishdwi's commentslogin

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.


Wow, this is really weird. I looked at the github and see you published benchmark updates in these sizes of N:

9 → 20 → 36 → 50

These are super arbitrary numbers of benchmarks to run (9, 11, 16, 14). I see a few explanations for this:

> Claude dropped "pathological trials" for you before publishing. This would make your results quite dishonest.

> You chose different sized task groups (almost certainly not the case).

> You excluded timed out trials, or something (also would be dishonest).

Hopefully there's a better explanation here!


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!


HN commenters shouldn't have to be Sherlock Holmes!

Extraordinary claims should be supported by evidence. You could have easily posted the seed, the 50 questions, and the results for claude and graft on each, but didn't.

I also see Graft got 16/16 on one update and 2/14 on another. Further evidence that each group of questions was selected somehow, not random.


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" and it hands the agent the right files and lines to start from, so it reads a lot less to get oriented.

so graft solves for making claude code understand your codebase every session.

And I feel you can save a lot more tokens and also increase accuracy by just switching to new claude session without worrying about your codebase context. (doesn't solve for the session context yet, but we are still figuring out how can we solve for that. Maybe hooks that can manage your CLAUDE.md)


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, while graphify only looks at names and file paths.

You feel it while working too. graft hands the agent the exact file and line it needs for each question, so Claude keeps using graft.

Same is true for any other cli tools, claude never actually uses them as it's trained to use grep. but for graft as we set the directive to use graft at the start of the session and before the turn, claude just knows graft exists and also get the relevant context without it going and calling tools it was not trained on.


Thanks, that makes sense. The “Claude actually uses it” part is especially interesting. I actually find it better this approach don’t add another skill Claude might ignore, but make better retrieval the default.


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.


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 the code is written.


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, a few of our contributors are working on making it better for java projects, let us know if you have any ideas there.


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 have run tests on DeepSWE as well which are long running tasks, we got 20% better accuracy on the tasks where sonnet 5 failed. didn't want to post that numbers yet as I think we can do better on DeepSWE and on a cheaper model like gpt-5.6-luna or grok-4.6


The graph is pre-filling the context that does the sync, right? Doesn't that create a bias towards what's already present? If anything hallucinated does make it in at some point, won't the sync just reinforce that hallucination if some new component touches the bad info, just like a long session rabbit-holing? New sessions, in contrast, have no contextual assumptions and often catch those problems.


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 calling our CLI tools instead of Grep.


I'm thinking more in terms of the case where my coworkers' agents aren't working via graft, and changes are made without the post-edit update hooks.


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


Oh, of course. Brilliant.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: