Import history from arg-specified file(s)

[mcint]

I’m suggesting that $ atuin import [shell] accept [file…] arguments.

• Currently: $ atuin import [shell]
• Proposed: $ atuin import [shell] [[-f] file...].

HISTFILE for my currently foregrounded shell reads /Users/user/.local/share/zsh/history/zsh.2026-03-17.6358.11444.log. I set it with HISTFILE=~/".local/share/zsh/history/zsh.$(date +%F).$$.$RANDOM.log", and on other systems I’ve used boot-ids in place of random.

With separate files, atuin can make a good-enough assumption that each file comes from one session. This assumption would provide a good interface for people to backfill & populate atuin-tracked history in different sessions. While I haven’t seen or leveraged session ids in history search, it seems helpful to share just particular sessions with llms, teammates, or export for personal notes or doc creation.

I will say also, I’ve been wanting to build http://cht.sh for self and group use, namely getting an edit & create (and moderation) story right. Atuin has the technical hard parts solved. Maybe ways to publish or share could give people more reason to talk to others about the tool & workflows.

Importing from per-directory-history

I’m coming over to Atuin from per-directory-history. I’ve used a simple python script to get all the data from it as a csv file which includes cwd, timestamp (in seconds) and cmd. I’m on a mac so I’ve used TablePlus to dig around in the Atuin history.db file. I’ve also seen from github discussions that if I do make changes in history.db I need to use atuin history init-store to update the records.db. What I’m looking for is info on how I should populate the columns I don’t have data for: id an…

Oop, again limited by discourse newbie, Trust 1, status to 1 link per post, even though 2/3 are internal to forum. Guess I’ll keep posting and reading :D.