![]() The system the message is special and can only be sent once at the beginning of a conversation. These indicate who is ‘speaking’ at any given moment in the conversation, or in other words whose ‘go’ it is. Fortunately, in the publically available API, there is no need to use these tokens as it’s abstracted away for you in the API like so:Ĭonversation messages fall into three message types: system, assistant and user. These tokens wrapped the messages between the user and the chatbot and delineate where messages start and end. In the alpha, we had to wrap our messages with some special tokens in order to get them to work – the, tokens were the most obvious. You’ll likely have seen this elsewhere, or in the docs, but the ChatGPT API works slightly differently from the standard playground models. Being able to say ‘Update my onboarding component to have a skip button taking you to the dashboard’ is an extremely powerful thing to be able to do in your codebase, it finds the context itself and is able to execute the change with immense speed and ease. I did over time however realise that there was real value to be had by linking the two technologies – essentially giving a chatbot, with all of its known capabilities and strengths regarding code writing and explanation skills, the context of your entire codebase, which is something that is currently not possible elsewhere. I was initially hesitant to add chat functionality to Buildt I have been worried that with that functionality would come lazy comparisons or pigeonholing of our product as simply ChatGPT that lives in VSCode when in reality the tech we’ve been building such as our semantic codebase search engine is so much more powerful and nuanced than that. ![]() We’ve been fortunate enough to have access to the ChatGPT alpha API through YC for the last two months.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |