My config file doesn’t do anything with db_path, so I 'm expecting it to be in ~/.local/share/atuin as the documentation says. (I’m on Ubuntu 26.04.) But the history.db file there hasn’t changed in over a month. But my commands are being saved. So where is it storing that?
How can I find out where atuin is storing the history? Or other configuration being currently used?
Atuin Doctor
Checking for diagnostics
Please include the output below with any bug reports or issues
{
"atuin": {
"version": "18.19.0",
"commit": "fb33978d9439ba7e97123c1adc932c6a74e3c8ae",
"sync": null,
"sqlite_version": "3.46.0",
"daemon_enabled": false
},
"shell": {
"name": "zsh",
"default": "zsh",
"plugins": [
"atuin"
],
"preexec": "built-in"
},
"system": {
"os": "Ubuntu Core",
"arch": "x86_64",
"version": "24",
"disks": []
}
}
Should the documentation be updated? Everything in your documentation leads one to think that the config and history will, for Linux users with no special changes, be saved to the XDG standard locations. But that’s not true if you install from the snap.
Hey! Thanks for reporting, glad you got it figured out
So: I have atuin installed from the snap, and, ugggh, it’s using its own special-snowflake directories.
Should the documentation be updated? Everything in your documentation leads one to think that the config and history will, for Linux users with no special changes, be saved to the XDG standard locations.
We do not support snap, and generally do not support versions installed by any method other than what we state on the docs.
Please use our install script wherever possible. We’ve had so many problems with other packaged versions that change the paths, change the code, or change our dependencies. Or are otherwise horrendously out of date
If the curl-to-bash is not ok for you, you can download a binary from our releases page, or use one of the supported manual installation methods: Installation - Atuin Docs