joshi4

I agree with what a lot of folks here are saying around knowledge transfer is a continuous/on-going process.

Any one-off knowledge transfer will most likely fail. People can't learn actionable knowledge with doing the actions. - That's why we need continuous sharing and doing.

People only look for the artifacts of a knowledge transfer when they need it. When resolving unfamiliar issues, people's first question is: "Has this happened before? How did we resolve it the last time?" It's a simple question but most often its very hard to answer.

The knowledge needed to answer questions like the one above, is mostly manually compiled together and often from memory.

Finally, actionable knowledge is hosted in the same tools as product specs, meeting notes, press releases etc. As a result, creating, finding and following such knowledge is quite hard.

Disclosure: I'm building Savvy(getsavvy.so) to fix a lot of these issues for developers.

I'm currently using GPT4-o via OpenAI's API.

I've been looking at ollama for a bit and I think I will ship an integration with Savvy at some point.

For enterprises, I think it makes sense to support a company approved LLM API endpoint in addition to local LLMs.

I'm happy to answer any questions you have around privacy too.

You're right. A runbook is more than just a list of commands.

I plan to add support for setting up and validating prerequisites for running a runbook with Savvy. For example, Savvy can ensure that all environment variables are automatically set up and removed as part of a `savvy run.`

A while ago, I built Flowshare, which is similar to Savvy but works in the browser. I will integrate that tech within Savvy to support capturing runbooks that involve steps in the browser and the terminal.

I like your suggestion on troubleshooting. Savvy can offer a great experience here as the cli will know when a command has failed or returned a nonzero exit code.

> but what if you rethought it to check in with the user step by step, telling them what they're about to do next

IIUC, your thoughts align with how Savvy Run currently works. Savvy suggests the next step, but devs can edit or ignore it. Providing troubleshooting help, as you suggested, will definitely improve the DX.

Savvy doesn't have SSH support, but I'm working to add it soon.

I think we can make SSH support work without installing Savvy on the remote machine, but I'm still working through the details.

I'm laser-focused on nailing the DX and making sure it delivers a lot of value to our users.

If you're up for it, I'd love to chat and learn more about how Savvy can help you personally and at work - my email is [email protected]

We don't see or store the output of your commands at all.

Your commands and the AI generated text for runbooks created using savvy record and savvy record history are stored in the database.

All data in the DB is encrypted at rest and during transit.

Any runbook, commands, or explanations generated with savvy ask/explain are ephemeral and not stored in our DB.