Alternatives
Products that do what Playbooks for your Terminal, replacing your shell's history does
- 1
- 2
- 3PJ
Hello everyone, Dipesh and Siddarth here. We are building PlayBooks (https://github.com/DrDroidLab/playbooks), an open source tool to write executable notebooks for on-call investigations / remediations instead of Google Docs or Wikis. There’s a demo video here: https://www.youtube.com/watch?v=_e-wOtIm1gk, and our docs are here: https://docs.drdroid.io/docs/playbooks We were in YC’s W23 batch working on a data lakehouse with support for dynamic log schemas. Eventually we realized it was a product in search of a market and decided to…
2024 · github.com
- 4
- 5
- 6
- 7
- 8
- 9WA
Hi HN community, I’m Zach, founder and CEO of Warp, and am excited to show you Warp, a fast Rust-based terminal that’s easy to use and built for teams. As of today, Warp is in public beta and any Mac user can download it. It works with bash, zsh, and fish. The terminal’s teletype-like interface has made it hard for the CLI to thrive. After 20 years of programming, I still find it hard to copy a command’s output; I always forget how to use `tar`; and I always have to relearn how to move my cursor. To fix fundamental accessibility issues, I believe we need to start innovating on the terminal,…
2022 · warp.dev
- 10SC
Savvy's CLI allows you to create, share, and run runbooks from your terminal. Savvy(getsavvy.so) natively integrates with modern LLMs and reduces the time to create a great runbook from minutes and hours to seconds. Savvy supports creating runbooks entirely with AI(savvy ask) or a human in the loop(savvy record.) Savvy Ask: Generate entire runbooks or a single command using natural language. Savvy Record: This creates a new subshell that automatically expands all aliases before recording commands locally. These commands are then sent to an LLM, which generates the first version of your…
2024 · github.com
- 11
- 12
- 13EA
Happy new year folks! This tool was born out of a situation where I had 'inherited' a bunch of servers that were not under any form of config management. Oh, the horror... Enroll 'harvests' system information such as what packages are installed, what services are running, what files have 'differed' from their out-of-the-box defaults, and what other custom snowflake data might exist. The harvest state data can be kept as its own sort of SBOM, but also can be converted in a mere second or two into fully-functional Ansible roles/playbooks/inventory. It can be run remotely over SSH or…
Jan 2026 · enroll.sh
- 14HY
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.
2022 · github.com
- 15
- 16
- 17
- 18IM
2024 · github.com
- 19
- 20
- 21
- 22DT
I got tired of open file.docx → wait 8 seconds → close Word just to read a document, so I built a terminal-native Word viewer! What it does: * View `.docx` files directly in your terminal with (mostly) proper formatting * Tables actually look like tables (with Unicode borders!) * Nested lists work correctly with indentation * Full-text search with highlighting * Copy content straight to clipboard with `c` * Export to markdown/CSV/JSON Why I made this: Working on servers over SSH, I constantly hit Word docs I needed to check quickly. The existing solutions I'm aware of either strip…
2025 · github.com
- 23HA
This 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…
Jan 2026 · github.com
- 24AI
2021 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →