Incorrect Model Requested about gptel HOT 7 CLOSED

Oops, thanks for catching that! Fixed in 444a431.

from gptel.

Further, from a fresh Emacs session, setting the gptel-model variable in config is not respected. I have it set to "gpt-4", but a new gptel invocation always starts with gpt-3.5-turbo with the value of gpt-model that I set myself overwritten.

from gptel.

Further again, even after evaluating (setq gptel-model "gpt-4") in the chat buffer itself it still calls the API via 3.5 turbo.

from gptel.

Didn't mean to close this issue yet. Did Github auto-close this because I said it's fixed in my above message?

from gptel.

@fosskers I take it from the reaction this is fixed now. Feel free to reopen this issue if not.

from gptel.

Uh oh...

HTTP/2 404 
date: Thu, 13 Apr 2023 05:37:31 GMT
content-type: application/json; charset=utf-8
vary: Origin
x-request-id: ac70f63f6b5951daddce9b5c16271406
strict-transport-security: max-age=15724800; includeSubDomains
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 7b715b885cc2af5a-NRT
content-encoding: gzip
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

{
    "error": {
        "message": "The model: `gpt-4` does not exist",
        "type": "invalid_request_error",
        "param": null,
        "code": "model_not_found"
    }
}

from gptel.

The consensus here seems to be that this is an issue on OpenAI's end; mainly that my account might not have GPT-4 access yet.

from gptel.