Savvy Run: Search and run runbooks from the terminal
Forget copy-paste: Savvy automatically suggests the next command on the CLI for you. All you need to do is press enter.
Savvy Ask converts natural language to shell commands.
Personalized: Savvy generates commands tailored to your OS
Stay in the flow: Upload files from the terminal. Slice and dice data in seconds.
Iterate: Refine your prompts to nudge Savvy to your desired solution
Savvy Explain helps you understand complex shell commands and errors.
Great for beginners and experts: Learn to use git or dive into ffmpeg and kubectl
RTFM? Not today: Understand error messages and flags without reading man pages
Pro tip: savvy explain !! explains your last command
savvy prompt
Savvy’s CLI automatically captures your shell prompt along with the command being executed.
It is vital to share the context within which a command or Runbook is executed and
shell prompts are highest density source of such context.
Savvy’s CLI eliminates the need to capture this context manually.
Savvy Prompts
savvy record
savvy record starts a sub shell that is identical to your usual shell with one extra addition: all your commands are recorded and used to automatically generate a runbook when you exit the shell.
savvy automatically expands all your aliases so anyone can copy paste the commands.
savvy record —ignore-errors
Users shared that runbooks for disaster recovery and business continuity often have upwards of 50 steps. Errors and typo’s are inevitable when creating such a long runbook. Manually finding those typos and deleting them can itself become a source of error.
Passing —ignore-errors to savvy record ensures any command that returns a non-zero exit code is automatically ignored.
savvy record history
Usually, we realize we should document/share something after doing it.
savvy record history allows you to create runbooks using your recent shell history.
Share Runbooks
Savvy runbooks are private by default.
Each runbook can be shared with your teammates using an unlisted link ( requires a savvy account to view) or make the runbook public to allow anyone with the link to view the runbook.
Only the owner of a runbook can edit the runbook or change its visibility level.
Checkout the public runbook from the examples above: