Adopt chat-extension-utils #86
Conversation
|
It's much harder to tell how tools will be used and how they are used in the prompt. I assume they just get run and the result is inserted into the prompt, but maybe harder to troubleshoot or adjust. Definitely nicer that I don't need to worry about caching tool results though - that part felt like the most obvious part that everyone would need. LGTM overall. |
There was a problem hiding this comment.
Yeah, but the idea is that you shouldn't have to do much troubleshooting, the library should do the right thing. Is there something that you expect having to adjust?
You do bring up a good point that it should give you a way to see the real prompt/request, maybe starting up the trace utility.
|
Yeah I think I would just want that visibility to confirm that it is getting the context correctly. |
|
I did add something to show the trace utility, it prints a message inline. I also opened this microsoft/vscode-prompt-tsx#134 |
|
Any other thoughts on this? It doesn't have to be merged, but it would be cool if it was |
|
Looks like this was depending on a version of the library that wasn't published yet, since I was working with |
|
will try it next time haha |
What do you think?
@amunger @eleanorjboyd @joshspicer
I think the big string prompt is a bit ugly, I'm thinking about supporting PromptElements for that.