[joh6nn]

- all the data is stored in a sqlite db, so it's actually structured, as opposed to just being in an adhoc text format

- this matters because it's capturing not just what commands were run, but metadata about the commands as well. Of particular interest to me is that ot captures the start and end time for every history entry so you can get timing data even if you forget to use `time`

- it provides much more fine-grained control over what makes it into the database than shells provide for controlling what makes it into their built-in history. For example, it has built-in support for filtering out common kinds of secrets/tokens/etc.

It's also in active development with a friendly and helpful creator/project lead, an active community, and an ever growing feature set.

I'd recommend giving it a try; as far as I'm concerned, it's best-in-class for managing shell history

[alchemist1e9]

> Of particular interest to me is that ot captures the start and end time for every history entry so you can get timing data even if you forget to use `time`

That’s potentially an incredible useful feature to integrate with all that metadata! Very very interesting.