ddworken

Including the server as part of the release sounds reasonable to me. I'm inclined to keep it as a separate file since most people don't need that feature, so I'd rather not unnecessarily increase the size of the main binary size. I filed https://github.com/ddworken/hishtory/issues/78 to track this.

See the self-hosting section in the readme, it is pretty easy to spin up a server. Or alternatively if you aren't using the syncing feature, see the offline install section which will completely disable the integration with the backend.

In general, having secrets in your shell history is an anti-pattern whether you use hiSHtory or not since it means they end up persisted on disk and unencrypted. hiSHtory respects the standard shell convention of prefixing commands with a space to avoid persisting them, so if you're already doing that then you're all set. In addition, you can easily delete history entries you accidentally record via the hishtory redact command.

Exactly! I also use it to sync between multiple personal computers for the exact same reason.

This actually does have both!