Feat: add debug option + logs, poll LLM for run status. #15
Conversation
lublagg
changed the title
lublagg
changed the title
| const { action, resource, values } = JSON.parse(toolCall.function.arguments); | ||
| const request = { action, resource, values }; | ||
| self.transcriptStore.addMessage(DEBUG_SPEAKER, { description: "Request sent to CODAP", content: formatJsonMessage(request) }); | ||
| const res = yield codapInterface.sendRequest(request); |
There was a problem hiding this comment.
This may be a later addition, but it seems like some sort of sanity checking before sending it direct to CODAP might be a good idea? Are there API calls that would cause real problems, or crash the page?
There was a problem hiding this comment.
I don't think there are any that will crash the page... I think at worst you would just get a { success: false } message.
In theory it could do something weird like create a request to delete something you don't want to delete. But, if we implement the undo/redo button functionality, I guess that would be a reversible scenario.
I think this will be something to keep in mind moving forward as we test it out with different inputs.
| description: "Get a list of all attributes in a dataset", | ||
| strict: true, | ||
| name: "create_request", | ||
| description: "Create a request to get data from CODAP", |
There was a problem hiding this comment.
Not just get data, right? It could create/alter/delete components as well.
There was a problem hiding this comment.
Yes -- it can use all of the available CODAP API create/update/delete endpoints.
src/utils/utils.ts
Outdated
| @@ -3,6 +3,22 @@ export const timeStamp = (): string => { | |||
| return now.toLocaleString(); | |||
| }; | |||
|
|
|||
| const idChars = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"; | |||
| export const createMessageId = (): string => { | |||
There was a problem hiding this comment.
Seems like this should have a comment saying why you're not just using a nanoid or some other standard random identifier.
There was a problem hiding this comment.
Ah, I hadn't thought of that - I just added in the nanoid package and am using that now.
This PR introduces several changes:
showDebugLogis set to true. By default, if the app is in dev mode,showDebugLogwill be set to true.startRunlogic and implements a new function inassistant-model.tsto continuously poll the LLM responses so that we can execute multi-step requests, and adds logic for handling error run statuses.create_request. This model has been given the CODAP API documentation in its instructions and generates the arguments for requests itself. We then construct the message from the arguments returned by the LLM, and send the request to CODAP.