Description
If I just pull up search in a new session without typing anything. [ SESSION+ ] and [ GLOBAL ] are indistinguishable. However once I start to type [ SESSION+ ] incorrectly (based on my understanding of the docs) matches [ SESSION ]. IE. It will only match commands from the current session not global plus the current session.
Additional Possibly relevant info
I recently upgraded to the latest version of atuin. I’d missed a few upgrades in between since my last upgrade. (And doesn’t seem I did my usual backup before this upgrade so not sure which version I upgraded from. Last backup was 2026-04-20 so likely when I last upgraded before this time).
I normally use [ DIRECTORY ] as my filter mode and then switch to [ SESSION+ ] if I’ve never run that command in the current directory. However I noticed that a command I expected to find didn’t show up. Once I switched to [ GLOBAL ] the command showed up and I realized I wasn’t getting the full history.
Output of atuin doctor
Atuin Doctor
Checking for diagnostics
Please include the output below with any bug reports or issues
{
"atuin": {
"version": "18.19.0",
"commit": "",
"sync": {
"auth_state": "Hub (legacy token — run 'atuin login' to upgrade)",
"auto_sync": true,
"last_sync": "2026-08-10 5:19:16.905629654 +00:00:00"
},
"sqlite_version": "3.51.3",
"daemon_enabled": true
},
"shell": {
"name": "nu",
"default": "nu",
"plugins": [
"atuin"
],
"preexec": "built-in"
},
"system": {
"os": "Ubuntu",
"arch": "x86_64",
"version": "22.04",
"disks": [
{
"name": "/dev/mapper/nvme0n1p6_crypt",
"filesystem": "ext4"
},
{
"name": "/dev/mapper/nvme0n1p6_crypt",
"filesystem": "ext4"
},
{
"name": "/dev/nvme0n1p5",
"filesystem": "ext4"
},
{
"name": "/dev/nvme0n1p1",
"filesystem": "vfat"
}
]
}
}
```