4 ms·
Hi HN, I built this because I'm tuning a bunch of prompts and don't have a great way to do this systematically. This CLI tool helps you pick the best prompt a
by typpo 3y ago
Hi HN,
I built this because I'm tuning a bunch of prompts and don't have a great way to do this systematically.
This CLI tool helps you pick the best prompt and model by allowing you to configure multiple prompts and variables. It outputs "before" and "after" so you can easily compare LLM outputs side-by-side and determine if the prompt has improved the quality of each example.
Example use cases:
- Deciding whether it's worth using GPT-4 over GPT-3.5
- Evaluating quality improvements to your prompt across a large range of examples
- Catching regressions in edge cases as you iterate on your prompt
It supports a handful of useful output formats: console, HTML table view, csv, json, yaml, so you can integrate into your workflow as needed. It also can be used as a library, not a CLI.
I'm interested in hearing your thoughts and suggestions on how to improve this tool further. Thanks!
- brianjking 3y agohttps://github.com/nat/openplayground https://github.com/nat/openplayground How does this compare to Nat's OpenPlayground? Vercel recently launched a playground too.
- typpo 3y agoLooks like the playground is mainly for comparison between models, not prompts, and doesn't support templating? Vercel's is similar but not free and open-source. I'm running these tests in bulk, so I prefer to automate with the CLI, or integrate with a test framework like Jest. I think the web UI is good for tinkering, but does not fit as well into real workflows.