7 comments

[ 4.3 ms ] story [ 17.1 ms ] thread
Why a complete rewrite rather than a wrapper around the cli commands?

Also, aren’t LLMs RLHFd a lot with using tools like git and as such have a better time interacting with it than custom tools?

Maybe I'm missing something. If I use `git status --short` or `git log --oneline`, I see output similar to your tool's.
check out rtk that does this for a bunch of commands
Was this entirely created by an LLM? The article clearly was.
The 71% reduction is interesting but I'd want to see where those tokens are actually going in a typical agent session. In my experience running multi-step coding agents, the git output itself is rarely the bottleneck...
You should expect to be gently ridiculed if you submit this as a serious project. Do not use LLMs to claim knowledge or abilities you don't actually have.

It's not impressive, and it's obvious to anyone with more than a year or two of actual programming experience.

So the big token saving was changing a setting that Git already allows you to change?

And does 8ms really matter when you're shunting bulk crap back and forth from the cloud?