2 ms·
To be clear, this would be an insane thing to actually run as it is. But you can run everything in dryRun if you just want to see what it would install. Altho
by empath-nirvana 3y ago
To be clear, this would be an insane thing to actually run as it is. But you can run everything in dryRun if you just want to see what it would install. Although, and i just realized this, it'll possibly generate different code after you set dryRun to false, so i need to fix that somehow.
- majormajor 3y agoThe idea I've had for things like this is a "run once and memoize" approach instead of regenerating each time. Kinda like a template, but with one key difference: if you only store the "template prompt" and modify that prompt you may get something pretty substantially different (and overly destructive a change!) from the original, so my idea there is to record the history of prompts + artifacts but always do modifications by asking GPT to apply a change to the memoized output, which then gets itself reviewed in dry-run before being saved.
- empath-nirvana 3y agoyeah that was what i was going to do, this is a spare time project though so it'll have to wait for the weekend. It does return the previous output on requests to update it, but it's by no means guaranteed to return the same results. It does most of the time, though, if the description hasn't changed.