Error: GPT-5 - 401

Open
#13,381 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 8 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
18/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active

Research direction

The payload names no file or entry point. Start by reproducing the 401 with an OpenAI model configured alongside a key that has a gsk_ prefix, then find where the provider's API key is read and sent. Done means the report's cause is confirmed, either a misconfigured key or a provider mix-up, with a clear message or fix. The reporter has not said which change is wanted, so confirm the expected behaviour with a maintainer before editing.

Written by the indexing model from the issue text.

Description

Error Details

Model: GPT-5
Provider: openai
Status Code: 401

Error Output

{"message":"Incorrect API key provided: gsk_jdam********************************************0Fmi. You can find your API key at https://platform.openai.com/account/api-keys.","type":"invalid_request_error","param":null,"code":"invalid_api_key"}

Additional Context
Please add any additional context about the error here

Dominant language
TypeScript
Stars
36.5k
Forks
5.6k
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from continuedev/continue

All issues in continuedev/continue

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.