@MolBioBoy instead of explicit "environments", would having something like a tagging system help? You could tag a prompt with #dev #staging #prod #do-not-touch etc π
hmm, I think that would help organization for sure, but when we have a git-like system where things are pushed to staging, have different prompt IDs to help with testing x staging prompt with x production prompt before releasing the x prompt into the wild, i think it could help in making sure your app is robust. right now we just push changes directly to main after changing a prompt and it could be dangerous in an app that's live
might also be an edge case of mine though, but I still think changes shouldn't be pushed directly to prod. maybe before publishing you could have a playground area where you can import a json test set or something like this? right now it's a manual process cause you need to input the variables by yourself
Oh that's a very interesting use case! I'm sharing this with the team, and totally makes sense - some way to have better control over what prompts go to production would be very useful