In Atuin v18.13, we released several new features, including daemon improvements, a PTY proxy, and AI integration. These new features are available by either enabling them in config, or by running atuin setup and accepting them in the wizard. Some users have raised understandable questions and concerns about the scope and direction of Atuin; this post is to clarify our current thoughts and intentions.
More than Shell History
I started Atuin as a tool to make shell history good. I was super frustrated by the existing search, and even more frustrated that I kept losing commands. Atuin solves that problem. In so doing, we built a pretty good generic sync engine! It can sync any small piece of data, not just bash.
After making shell history better, it became pretty clear that there was room to improve other aspects of the shell, too. We used our existing tooling to build a bunch of other features! atuin dotfiles, atuin kv, atuin script are all based on the same underlying primitives.
Alongside, we’ve experimented with building out Atuin Desktop, to try and make operational, terminal-based workflows easier to collaborate on and share. Our mission has expanded from just making shell history magical, and now encompasses the goal of making the rest of the terminal + shell experience magical too.
Why AI?
We’ve turned down AI features in the past when they were brought up. Why change our minds now? The short answer is that AI has shifted in two major ways: current models are much more capable, and AI’s use has become much more ubiquitous. The models of 2024 are really not comparable to the models of 2026.
One of our main concerns when considering adding AI related features to Atuin has been accuracy. We don’t want an LLM to hallucinate arguments or even entire commands. Recent frontier AI models have gotten quite good at this, and while it’s not perfect, we believe we have the ability to implement this in a way that makes it very accurate and improves your day-to-day experience in the shell.
Further, the use of AI coding assistants has gotten extremely popular, and agents are running commands on machines with minimal visibility. Back when we first released Atuin, the user was the only one running bash on their machine. This is no longer true.
Atuin is uniquely positioned to be able to provide observability into what those agents are doing; think intent, context, and audit trails.
Addressing Concerns
It’s understandable that many users prefer a simple, uncomplicated tool to just manage shell history. We get that, and we want to continue being that, as we have for the past few years. But we also want to explore what it could mean to make the rest of the terminal experience magical.
As we develop new features and tools, this is what we want to commit to:
- Your data does not leave your machine without your permission
- Atuin’s core will always be good, fast shell history + sync
- New features and workflows are opt in. They do nothing if you don’t use them, and if you really don’t want them in your binary, they can be compiled out