Ellie Huxtable

Just shipped something new in Atuin 18.5: Scripts 

You can now turn shell history into reusable, synced, and encrypted scripts.

✨ Built from real commands
✨ Supports variables + templating
✨ Custom shebangs (Python, etc)
✨ End-to-end encrypted + syncs across devices

This has been super useful already. I use it for deploy commands, fiddly git commands, and other things I forget a bunch.

Blog post with details: https://blog.atuin.sh/atuin-scripts-shareable-syncable-shell-snippets/

Would love to hear what you think! Feedback very welcome <3

Atuin Scripts: Shareable, Syncable Shell Snippets

Atuin supercharges your productivity by enabling you to rapidly retrieve any command you’ve ran, at any time, from anywhere. It stores your shell history in a database, recording additional command context and syncing it (e2e encrypted) across devices. Get started here Your shell history holds a record of your

The Atuin Blog
Apr 9, 2025 at 4:46pmWeb
Show threadSebastian HoßApr 9, 2025
@ellie nice stuff! It would be cool if scripts could be scoped to a folder so that my 'deploy' script in one project can be different in another project. Likewise, it would prohibit me from running a dangerous script in a folder by accident?
Show threadSebastian HoßApr 9, 2025
@ellie oh and about template values: What I'm typically doing is to allow passing in values (e.g. '-v env=prod') or if no value was given run some script that determines all possible values and pass that through fzf to allow an interactive selection. This is really useful for long, complex or hard to type values. Since atuin already has a fuzzy matcher, how about allowing to specify some sort of 'completer' per template value? That completer could just be another script returning all values..