make chat() generic

[romainfrancois]

wrt to its first argument, and add methods for :

• character : like the one we currently have
• chat_tibble: so that we can have follow up conversations with the 🤖 , should chat_tibble be renamed conversation or just chat ?

[JamesHWade]

I say stick with chat. A lot of users will assume that chat includes conversation history.

[romainfrancois]

I like it. I guess than we'd need some functionality to mesh together history and a new thing

x <- chat("hello")
chat(list("say that in Italian", x))

or perhaps

chat(list(user = "hello", assistant = "...", user = "...", x))

... actually that might be a user case for ... I'll play with this

[JamesHWade]

If we can, I'd like the prompt for the user-facing chat() function to always expect a character rather than a list. Or at least, it would be great if chat(prompt = "my prompt") still works.

We came up with a series of s3 objects in gptstudio to generically handle:

• building a prompt and associated configuration options
• performing the api call
• processing the response

I'm intrigued by .... The approach in gptstudio works, but it feels a bit too complicated.