Atuin v18.13 – better search, a PTY proxy, and AI for your shell
18 points by msangi
18 points by msangi
I've been using atuin since shortly after i first heard about it, must have been years by now. At the time it was a nice upgrade over fish's already pretty good history access, with added sync.
Too bad the LLM integration has been built directly into the core instead of an additional component. This might prevent some people from continuing to use it due to work restrictions (at least that was the case when iTerm2 integrated features of this sort, but that's been a while back).
I've come to really dislike how some of these more recent command line tools start to acquire features outside of their core functionality at some point in their lifetime. I suppose it's a function of being the pet project of a singular maintainer (or a small group), instead of a (UNIX-y) tool to solve a particular problem, that needs to be able to generate constant attention and issue backlogs to attract enough financial backing.
This always causes a nagging "this-is-too-much-to-depend-on" feeling in me. The more complex something is, the less I believe in its longevity. Since I do not actually need the sync (what I do is usually trivial or heavily tied to specific machines), and never modified my atuin config after initial setup, I guess I'll try to drop down to fzf's shell integration and see what I'm missing.
By the way, who pays for the LLM? The blog only mentions a "we" that does all the doing.
I've come to really dislike how some of these more recent command line tools start to acquire features outside of their core functionality at some point in their lifetime. I suppose it's a function of being the pet project of a singular maintainer (or a small group), instead of a (UNIX-y) tool to solve a particular problem, that needs to be able to generate constant attention and issue backlogs to attract enough financial backing.
Agreed. I think that Atuin is trying to pivot into a business model where they either get bought out by the current crop of LLM providers, or become a useful enough tool that developers plug into a subscription for access to LLM whatever for their command-line usage.
I don't blame people for wanting to get paid and do well, but yeah, small useful tools doing the thing that they were designed to do are no longer the thing. People see tools like uv and just imagine the buyout money.
Frustrating that I'll have to fork Atuin, too, to avoid AI garbage. At least make it an optional plugin, people.
pretty much all of atuin's feature can be disabled at compile time, including ai. also not enabled by default, even if it exists in the binary.
While I support you getting your bag, which I presume is what's happening here, I continue to wish this code were not a part of the core distribution of the software, because I consider it unethical to promote AI products.
I don't wish to argue; I just feel it's important to be explicit about these things.
I'm in the same boat as kolja. I have been using atuin for a few years now and kept my initial config unchanged.
I also use LuLu as a network firewall and lately, I've started noticing more and more "requests" from Atuin to connect to a remote endpoint when I press the up-arrow to access my shell history. It might be a completely benign request, but concerning nevertheless.
I'm on the lookout now for a simpler tool that does the job.
"requests" from Atuin to connect to a remote endpoint when I press the up-arrow to access my shell history
That's our update check. Code for it is here
Config to disable it is here: https://docs.atuin.sh/cli/configuration/config#update_check
You can compile it out with the update-check flag.
As someone who uses my shell history as an informal set of notes, I'm a huge fan of atuin. Happy to see an AI integration, and of course it's implemented with sane defaults (opt-in, shares almost nothing by default).