3 ms·
One of the most challenging aspects is having a proper interface for prompt management. Right now there are 5 different elements that are combined together to f
by nico 3y ago
One of the most challenging aspects is having a proper interface for prompt management. Right now there are 5 different elements that are combined together to form the prompt in a specific format. The prompt elements are stored in the .env file, are are read from there when running the app
Would love to get some tips or ideas on how to allow the user to manage the prompt, to make changes and test it (without braking it), from the command line
- john-radio 3y agoWell, you could throw in something like this - https://github.com/nicobrenner/commandjobs/compare/master...BenQuigley:commandjobs:master https://github.com/nicobrenner/commandjobs/compare/master...... You can also go further by writing code that prompts the user for these values, one by one, and stores them in a config file. But for a CLI application, you might reasonably wonder if the juice is worth the squeeze there. CLI users tend to be comfortable editing a config file to hold a secret. Edit: or if some of those values are actually optional, then you would maybe exclude them from this check.
- nico 3y agoThank you so much Excellent contribution, definitely need a ton of validations! Also pending is getting some tests in there, especially to test consistent LLM/GPT-dependent behavior Totally right about the difference in expectations from a cli user pov. I just want to make sure this tool is helpful to more people than just myself