HiSHtory: Your shell history in context, synced, and queryable
hiSHtory is a better shell history. It stores your shell history in context (what directory you ran the command it, whether it succeeded or failed, how long it took, etc). This is all stored locally and end-to-end encrypted for syncing to to all your other computers. All of this is easily queryable via Control-R and via the hishtory CLI. This means from your laptop, you can easily find that complex bash pipeline you wrote on your server, and see the context in which you ran it.
HiSHtory: Your shell history in context, synced, and queryable launched on November 1, 2022 with 179 votes, #173 of 3,471 launches that month and more than 95% of that year's launches. The site was still online in September 2026, 3 years on.
In plain words
HiSHtory is a shell history tool that records commands with contextual information including the directory, exit status, and execution time. It stores data locally with end-to-end encryption for syncing across multiple computers. Users can search their command history through Control-R or the command-line interface, making it easy to locate and review commands executed on different machines with full context about when and where they ran.
written from the facts on this page · September 2026
From the sources
Your shell history: synced, queryable, and in context - ddworken/hishtory
Does a similar job
all alternatives →
Hc: an agentless, multi-tenant shell history sinkJan 2026 · github.com · ▲43This project is a tool for engineers who live in the terminal and are tired of losing their command history to ephemeral servers or fragmented `.bash_history` files. If you’re jumping between dozens of boxes, many of which might be destroyed an hour later, your "local memory" (the history file) is essentially useless. This tool builds a centralized, permanent brain for your shell activity, ensuring that a complex one-liner you crafted months ago remains accessible even if the server it ran on is long gone. The core mechanism wants to be a "zero-touch" capture that happens at the connection…
HSTR – easily view, navigate, search and manage your shell history2018 · github.com · ▲33Bash and Zsh shell history TUI suggest box - easily view, navigate, search and manage your command history. - dvorka/hstr
Private cloud shell history. Open source server for bashhub2020 · github.com · ▲46Private cloud shell history. Open source server for bashhub https://github.com/rcaloras/bashhub-client - nicksherron/bashhub-server
- QBQuickly browse the history of any GitHub file2019 · githistory.xyz · ▲407
Quickly browse the history of a file from GitHub, GitLab, Bitbucket or any git repository
Smarter Shell History for ZshAug 2026 · github.com · ▲16Smarter shell history for Zsh. Contribute to overflowy/zhist development by creating an account on GitHub.
More dev tools this month
the category →
open-source IDE for thoughtful software design. Contribute to devdotfast/whiteboard development by creating an account on GitHub.
Dev tools · 28d ago · github.com
Contribute to reladraw/reladraw development by creating an account on GitHub.
Dev tools · 26d ago · github.com
OpenBot▲362Grok Bot alternative: free, local, open-source, multiplayer
Dev tools · 24d ago · openbot.run
Talanoa▲346Hi HN, I’m a fullstack developer, and honestly, I’ve lost count of how many side projects I’ve worked on over the years. But one idea kept coming back to me: a different kind of email client. It first came to me in 2014: “What if we could handle emails more like conversations?” Every year, I’d revisit this concept in my “Build Notes.” Ten years later, no one had built exactly what I had in mind — so I finally decided to do it myself. That’s how Talanoa was born. I wanted something focused on people, not timelines. I was tired of marking messages as unread just to remember to reply later, or…
Dev tools · 21d ago · talanoa.email
CoreSpeed▲332One MCP for everything your agents need: apps, memory, tools
Dev tools · 29d ago · corespeed.io
Source: Show HN post ↗
Launched alongside, November 2022
the whole month →
I made a thing! In 2014, I was holding a stack of iPhones and thought to myself: "Hey, if I had each phone display a playing card, I could click a button and they'd shuffle themselves" I pared that idea all the way down to this: trading cards made of e-ink displays. Right now, each card costs me about $20 each, but with only a bit more scale, I think I can get that down to $10. In doing this project, I learned how to design electronics and circuit boards. I learned Rust and wrote my first driver, I upped my CAD skills, 3D printed, and did my first resin casting. I generated the images on the…
Dev tools · 2022 · wyldcard.io
