Concern: you mention it supports the actual ChatGPT Web API -- isn't this against their terms of service? I'd be wary of publishing something that hits internal APIs.
Suggestion: I would rename what you call the "ChatGPT" (non-web) part of the backend to "OpenAI API" instead. There is already enough confusion in the world between ChatGPT and API access to the underlying GPT models.
There seems to be two extensions, one called "chatgpt" and one called "chatgpt-web" (https://github.com/chieapp/chie/tree/main/src/extensions). The latter seems to be using https://chat.openai.com/backend-api/conversation which is OpenAI's private API for ChatGPT. Using this (as a user) seems to be able to get you banned, as far as I can tell by some reddit posts as of late.
However, the extension called "chatgpt" seems to correctly use the right endpoint: https://api.openai.com/v1/chat/completions, but it's not ChatGPT anymore when you use it, so the naming is a bit confusing as you said.
Once I tried asking ChatGPT it immediately replied "You exceeded your current quota, please check your plan and billing details" which I can't believe is the case.
I then tried to press the copy button over this reply to paste it here but that raises an error: "TypeError: Cannot read properties of undefined (reading 'content') at #copyTextAt (chieapp.exe\asar\dist\view\chat-view.js:1:11362).
Due to the future relicense, contributors will be asked to sign an agreement.
EDIT: Never mind this is mentioned in the technical details link, thanks!
In the future, would you add support for local LLMs, such as LLaMa?
> NOT a webview wrapper of web pages.
but further down the page:
> The chat messages are rendered in a system webview. To minimize performance penalty the webview only renders a static HTML page with very limited JavaScript code.
> The chat messages are rendered in a system webview.