Fixing Shell History That Doesn't Persist or Save Correctly
Commands from an earlier session seem to vanish, or history from multiple open terminals overwrites itself instead of combining. Here's how history file writing actually works, and the specific settings that fix each symptom.
Shell history that seems to disappear between sessions, or that gets overwritten rather than combined across multiple open terminals, comes down to specific, identifiable settings governing when and how the history file actually gets written.
Step 1: identify the exact symptom
History from yesterday is completely gone → likely overwrite,
not append, behavior
History works in one terminal but not visible in
a different, simultaneously open terminal → expected default
behavior without explicit history sharing enabledStep 2: check whether Bash is appending or overwriting on exit
shopt -s histappendAdd this to .bashrc — without it, each Bash session overwrites the history file with just its own session’s commands when it exits, rather than adding to what was already there, meaning the last session to close “wins” and earlier sessions’ history is lost.
Step 3: check your HISTSIZE and HISTFILESIZE settings
echo $HISTSIZE # commands kept in memory during the session
echo $HISTFILESIZE # commands kept in the history FILE on diskA HISTFILESIZE set too low silently truncates older history entries from the file, even with histappend correctly enabled — check both values are set to something reasonably large if you want extensive history retained.
Step 4: enable live history sharing across simultaneously open sessions in Zsh
setopt APPEND_HISTORY
setopt SHARE_HISTORY
setopt INC_APPEND_HISTORYWithout these settings, each open Zsh session only writes to the shared history file when it exits — SHARE_HISTORY makes history genuinely live-shared across every currently open session, and INC_APPEND_HISTORY writes each command incrementally as you run it, rather than only at session exit.
Step 5: check for a corrupted or overly large history file
wc -l ~/.bash_historyAn extremely large history file can, in some configurations, cause slow shell startup or unusual truncation behavior — trimming it to a more reasonable size (keeping the most recent N lines) can resolve both performance and consistency issues simultaneously.
Step 6: check for HISTCONTROL settings unexpectedly excluding commands
echo $HISTCONTROL
# ignorespace: commands starting with a space are excluded
# ignoredups: consecutive duplicate commands are excluded
# erasedups: all previous duplicate entries are removedIf specific commands seem to be missing from history entirely rather than the whole file being affected, check whether HISTCONTROL is configured to deliberately exclude commands matching certain patterns — this is often intentional (excluding commands starting with a space, commonly used for commands containing sensitive values) rather than a bug.
Step 7: verify the fix by testing across an actual new session
# run a distinctive test command, close the terminal fully,
# open a new one, and check that the test command appears
# in historyTesting across a genuinely new session (not just the current one) is the only way to confirm persistence-related settings actually took effect, since the current session’s in-memory history behaves normally regardless of file-writing configuration.
Step 8: check for multiple, conflicting configuration files
# a HISTFILE or history-related setting defined in
# multiple sourced files (.bashrc, .bash_profile,
# a separately sourced history-specific config) can
# have the last-sourced one silently winIf a fix doesn’t seem to take effect despite being correctly written, check for the same setting being defined elsewhere too, potentially overriding your intended configuration later in the shell’s startup sequence.
Why history behavior differs so much between “just works” and “commands vanish”
History persistence isn’t automatic by default in the way many users assume — it depends on specific settings governing append-vs-overwrite behavior, file size limits, and (for multiple simultaneous sessions) explicit history-sharing configuration, all of which have to be deliberately set correctly for history to behave the way most users intuitively expect it to.