Thread

1. lukax · 1789622845 · focus · HN ↗

   What matters more is that you use the tools that the target model was fine-tuned on.

   E.g. for editing files with Claude models you should use Edit(file_path, old_string, new_string, replace_all) but with GPT models you should use apply_patch_call(patch) (where patch is a custom patch string with custom grammar).

   It appears newer models are better at narive harness tool calls and worse at custom tools that look similar to default tools.

   <a href="https:&#x2F;&#x2F;lucumr.pocoo.org&#x2F;2026&#x2F;7&#x2F;4&#x2F;better-models-worse-tools&#x2F;" rel="nofollow">https:&#x2F;&#x2F;lucumr.pocoo.org&#x2F;2026&#x2F;7&#x2F;4&#x2F;better-models-worse-tools&#x2F;

   1. nativeit · 1789623558 · focus · HN ↗

      I’m not really a dev, so hefty pinch of salt with this take, but doesn’t this feel like we’re just inventing new “fuzzy” regex with much more required compute?

      1. shepherdjerred · 1789623967 · focus · HN ↗

         comparing LLMs to regex is like the OG dropbox comment (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9224">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9224).

         I can understand this take 4-5 years ago but I have no idea how that&#x27;s your position in 2026

Unofficial Hacker News client; not affiliated with Y Combinator.