Install hishtory with Homebrew, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• hishtory

Project history

The repository begins on 2022-01-08 with commits for versioning, local and remote client separation, integration tests, installation, command timing, export, and web/backend pieces. The first public tags appeared in April 2022, with v0.1 and several subsequent tags on 2022-04-08.

The README presents the project as better shell history: command, working directory, exit status, runtime, host, user, and time are queryable through the CLI and terminal UI. It also documents a local SQLite database path for power users and encrypted synchronization for multi-machine setups.

Later docs added stronger offline options. The offline binary documentation describes install-time sync disabling, config-time sync disabling, and a build tag that statically links network-disabled code for users who want the binary to avoid HTTP requests.

Adoption history

hiSHtory's adoption path is tied to shell integration rather than a language ecosystem. The install flow wires it into bash, zsh, and fish, then maps Control-R to the search UI so users can replace a built-in shell habit without learning a separate command first.

The Homebrew and Nix packages make it available to users who prefer package managers over the curl installer. The README also documents multi-computer setup with a secret key, self-hosted sync servers, SQLite or Postgres backend persistence, and S3-compatible storage.

How it is used

Users query history by opening the TUI with Control-R or by running `hishtory query`. The query language supports text terms plus filters such as hostname, user, exit code, and before/after dates. The README also documents redaction, duplicate filtering, displayed-column customization, custom columns, color schemes, default filters, and direct SQLite access.

For sync, hiSHtory stores data locally and sends encrypted history to a backend. Users can run without sync, self-host the backend, or use an S3-compatible backend. That range matters for shell-history tools because command history can contain sensitive operational context.

Why package nerds care

hiSHtory is significant because it packages shell memory as a database-backed, queryable, syncable tool while still preserving the muscle memory of Control-R. It is part of the same packaging niche as Atuin and older SQLite-backed shell-history experiments.

The package is also interesting for its privacy trade-offs. It offers a central sync service for convenience, but its docs also describe offline installs, self-hosting, and a compile-time network-disabled binary. That makes it unusually explicit about deployment modes for a developer productivity CLI.

Timeline

• 2022-01-08: Repository history begins with versioning and client split commits.
• 2022-03-29: Website, install, update, status, Postgres setup, and backend work appear in repository history.
• 2022-04-08: First public v0.x tags appear.
• 2022: README documents contextual shell history, encrypted sync, bash/zsh/fish install, and Control-R search.
• 2025: Repository tags continue through a large v0.x sequence.

Related projects

• Atuin is the closest well-known related package, also replacing shell history with contextual records and optional encrypted sync.
• zsh-histdb and other SQLite shell-history scripts are adjacent earlier approaches.
• SQLite and Postgres appear in hiSHtory's official materials as local and backend persistence options.

Sources

• Official Git repository tags and commits for timeline dates.
• Official README for core behavior, query syntax, sync, TUI, self-hosting, and configuration.
• Official offline binary documentation for non-networked deployment modes.