Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not using the ChatGPT API #1

Open
protodave opened this issue Dec 13, 2022 · 4 comments
Open

Not using the ChatGPT API #1

protodave opened this issue Dec 13, 2022 · 4 comments

Comments

@protodave
Copy link

protodave commented Dec 13, 2022

Nice work, and useful to have GPT-3 access directly in Slack. And cool to see the Slack next-gen platform in action... and Deno too!

One clarification you might want to mention in your README... this isn't using ChatGPT, which doesn't have a released official API yet.

This is using the completions endpoint, which is fine for zero-shot scenarios, but it isn't stateful or conversational (not maintaining a conversation_id/parent_id that ChatGPT uses, for example).

This also uses the text-davinci-003 model, which is part of the GPT-3.5 series like the ChatGPT model, but they are distinct.

Though some folks have reverse-engineered the ChatGPT API and have released libraries to access the unofficial API until the official one is available:

Node:
https://github.com/transitive-bullshit/chatgpt-api

Python:
https://github.com/acheong08/ChatGPT
https://github.com/rawandahmad698/PyChatGPT

@fxchen
Copy link
Owner

fxchen commented Dec 16, 2022

Hey there! Appreciate the clarification. I'll add a note this uses the GPT-3.5 API (but lacks iteration cycles that's useful in the magic in ChatGPT).

The session-based ChatGPT packages have browser-based workarounds that are still unsupported by the official API thus far.

I'd like to build threads for iteration once the API is supported in OpenAI. A natural extension of SlackGPT would be using threads to keep / pass state back to OpenAI's future ChatGPT.

@protodave
Copy link
Author

A message thread would be a great fit to manage an ongoing ChatGPT session, good idea! And I suppose you could maintain the conversation_id/parent_id state either in the metadata for the messages and responses, or maybe somehow in the thread itself if that allows for custom metadata fields.

@fxchen
Copy link
Owner

fxchen commented Mar 20, 2023

Hey @protodave! I had a chance this morning to update and implement the tool against OpenAI's new Chat Completions API.

Building threading could be useful if there's interest!

@BigBerny
Copy link

Building threading could be useful if there's interest!

That would be awesome. To predict it should also only use the input from this thread. This could also improve the quality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants