[CGamesPlay]

I’m convinced that the best way to do this is actually to have a local daemon that exposes itself as a regular ChatGPT plug-in with the necessary features. That way, we can use the regular ChatGPT GUI, but it can still access whatever we like. This should work since IIUC all ChatGPT plug-in API calls happen on the client computer already.

[vorticalbox]

They do, chatGPT returns a list of tools it wants (this the right term?) to call and the arguments to call it with.

Up to the developer to map the args to the function and give the result back in the message history.

[CGamesPlay]

You misunderstood me. I’m saying instead of being a GUI, this could be a ChatGPT plug-in. That way the developer can focus on providing a smart API that does what the user wants, and not wasting time writing a GUI.

[kordlessagain]

Why is writing a better UI a waste of time?

[fzzzy]

Plugins use webhooks; tools work the way you describe.