Have something to say?
Support tagging Workflows
From Kathleen on PH: One suggestion it that could Savvy support tagging or categorizing workflows so teams can organize their knowledge better.
Iterate on prompts AFTER executing command suggested by savvy ask
Sometimes, its not obvious if a command is correct or wrong until users execute it. After executing it and viewing results, users should be able to iterate on the prompt.
Stream commands from CLI to Slack
Stream your CLI commands from your terminal to a slack channel. To start: savvy record —target=slack The above command will: Start a new sub-shell Check if the user has connected to Slack. Ask the user to select a channel. Confirm. Continuously send all commands to a slack thread. To stop: exit/ctrl-d
Detect if the user can run a artifact
Do they have all the commands installed? Be sure to handle compound commands like: foo; bar; baz;
Detect unreferenced variables in a Savvy Artifact
Surface these as errors/message for the user to fix them.
Support Fish
Savvy already supports bash and zsh. Fish is probably the #3 most common shell and it makes sense to support it.
Save CLI commands locally and attach them to tickets in an issue tracker
Provide detailed steps that document a bug or unexpected output. Integrate with Linear/JIRA etc to automatically attach the report.
Install Savvy with brew/apt
curl is convenient but for many users that install/reinstall deps and os a lot, it is better to integrate with their native package managers.
Local Redaction
Let me redact sensitive information like API keys, passwords, customer IDs, customer names, and PII before any data leaves my machine.
Support Local LLMs
Usage in no-network conditions, data protection, ability to choose specific models for specific kind of workload (for example fine-tuned) From: https://github.com/getsavvyinc/savvy-cli/issues/127