Release 18.13-beta

Releases
1

I just released 18.13.0-beta.1, with more fixes and some notable new features

New binaries

We’re experimenting with tighter LLM integration with the shell - currently LLMs have a ~30% error rate when generating bash. But what if we could make it good?

This is optional, and included in a separate binary. If you don’t want to use it, you don’t have to, and nothing will change for you.

To try out atuin ai, run

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/atuinsh/atuin/releases/download/v18.13.0-beta.1/atuin-ai-installer.sh | sh
echo 'if [ -x "$(command -v atuin-ai)" ]; then eval "$(atuin-ai init)"; fi' >> ~/.zshrc

And then press ? at an empty prompt to use our interface. It will authenticate at first use.

Daemon autostart

The atuin daemon has been marked as experimental for a long time, but going forwards we will be working to stabilize it.

This release includes the ability for Atuin to auto-manage the daemon background process - ensuring it’s running, healthy, and the correct version

Add

[daemon]
enabled = true
autostart = true

To check it out

Context switching

Many users have asked us about context-switching. With this release, it’s now possible to explore the context of a past command

With a history result selected, run c-a, c to zoom in on that execution context, and browse what happened around that time.

Installation

To update to the latest prerelease binary, run atuin update --prerelease

Changelog

Bug Fixes

  • (deps) Add use-dev-tty to crossterm in atuin-ai (#3185)
  • (docs) Update Postgres volume path in Docker as required by pg18 (#3174)
  • Systemd Exec for separate server binary (#3176)
  • Multiline commands with fish (#3179)

Features

  • (docs) Add Shell Integration and Interoperability docs (#3163)
  • switch-context (#3149)
  • Add Hub authentication for future sync + extra features (#3010)
  • Add Atuin AI inline CLI MVP (#3178)
  • Add autostart and pid management to daemon (#3180)
4 Likes
2

With a history result selected, run c-a, c to zoom in on that execution context, and browse what happened around that time.

Great! This should make it easy to migrate complex sequences of commands to Atuin Desktop.

1 Like
3

Exactly. I am really happy about this—truly a magnificent improvement.

1 Like
4

I just saw feat: Initialize Atuin AI by default with `atuin init` by BinaryMuse · Pull Request #3255 · atuinsh/atuin · GitHub getting merged.

Are you really sure you want to opt-in every user the Atuin AI feature? If this is introduced as on-by-default I, as a user, would not expect this to be in a minor release of a tool that sync my shell history.

I do love Atuin and what it provides, yet this feels like a HUUUGE step from the projects own definition “:sparkles: Magical shell history” to “Atuin AI lets you generate shell commands from natural language, right in your terminal.”.

1 Like
5

We haven’t released this just yet, but it will be gated behind an atuin setup command, which will explain what it is, what is/isn’t shared, and enable you to configure what features you want.

“opt-in by default” in this case just means… include it in the binary. We don’t share any data, we don’t break the privacy boundary we already have, etc.

I’m working on a post about this now, but we haven’t just had shell history for a long time. atuin scripts, atuin dotfiles, atuin kv, etc. There’s a lot of things that can be improved, that fit well within the scope of “making the shell better”. Every additional feature we ship, can be enabled/disabled, or even compiled out of the binary via feature flags.

Additionally - we don’t follow semver for features like this, and never have. The major version is an indicator of sync protocol support, and bumping this to v19 would mean no v19 client would sync with a v18 server.

Otherwise, another thing that will be included within atuin setup is a bunch of changes to the daemon. It includes a new fuzzy search mode that should be at least as good as fzf - have you checked that one out yet? I think you had issues with it before too.

6

Perfect. Thank you!

Thank you! I really respect your strict ‘we don’t want see your data ever ever’ policy and trust you to do the right thing. Almost certainly I interpreted the changelog entries without the full context on how you plan to roll out this new feature.

I wanted to voice concerns as soon as possible – those have been resolved now.

Yes, I do actually have seen this. The stuff in quotes was just a copy&paste from the GitHub repo title. I do confess it was provocative. I tried to communicate that this new AI functionality would be way more than just storing and syncing shell history and goes beyond what the repository title “advertises”.

I have not but will definitely check it out! :slight_smile:

2 Likes