Savvy – Capture and Share CLI Workflows in Seconds
Ever solved a tricky problem at the command line, only to struggle documenting it later? I built Savvy so you can capture and share your CLI solutions in seconds. With a simple savvy record history command, you can: - Go back in time and cherry pick commands from your shell history - Automatically expand aliases - Redact sensitive information locally - Convert hard-coded values into runtime placeholders - Export locally to markdown files or create shareable team workflows using Savvy. Savvy never reads command outputs - you explicitly choose what to share. When running workflows, Savvy…
In plain words
Savvy is a command-line tool that lets developers quickly capture, document, and share shell workflows. Users can select commands from their history, automatically expand aliases, redact sensitive data, and convert hard-coded values into placeholders before exporting to markdown or creating team workflows. The tool runs in a sub-shell to guide users through each step with runtime values handled automatically. It supports bash and zsh with beta Fish support.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
Ever solved a tricky problem at the command line, only to struggle documenting it later? I built Savvy so you can capture and share your CLI solutions in seconds. With a simple savvy record history command, you can: - Go back in time and cherry pick commands from your shell history - Automatically expand aliases - Redact sensitive information locally - Convert hard-coded values into runtime placeholders - Export locally to markdown files or create shareable team workflows using Savvy. Savvy never reads command outputs - you explicitly choose what to share. When running workflows, Savvy guides you through each step in a new sub-shell, handling all runtime values automatically. Some FAQs Q) How Does Savvy’s CLI work? Savvy’s CLI uses shell hooks (full support for bash and zsh. Fish support is in beta) to capture commands. Savvy’s CLI never looks at any command outputs or active keystrokes. Users have to explicitly opt-in (by typing savvy record/savvy record history) to capture commands every single time. Once you select a particular workflow with savvy run, savvy starts a new sub-shell and walks you through each step of the way. No manual copy paste or editing commands to provide run time values. Demo: https://getsavvy.so/demo Q) How does Savvy Auto-generate Workflows? Savvy takes your redacted commands as input and uses Llama 3.x hosted on Groq to create a first draft of your workflow. Q) What other LLM’s do you use? Savvy ask/explain are powered by GPT 4/GPT4o to convert natural language to shell commands and vice-versa. Try it out: GitHub: https://github.com/getsavvyinc/savvy-cli Demo: https://getsavvy.so/demo Docs: https://docs.getsavvy.so/guides/quick_start/ Example workflows: https://getsavvy.so/#examples Drop a comment below if you have any questions.
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 1d ago · opentrailpaper.com
