Fix get_auth_status response when using custom provider #3581
+97
−27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pakrym-oai
approved these changes
Sep 15, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses an edge-case bug that appears in the VS Code extension in the following situation:
auth.jsonfile.config.tomlto specify a custom provider.The profile menu in the VS Code extension will indicate that you are logged in using ChatGPT even though you're not.
This is caused by the
get_auth_statusmethod returning anauth_method: 'chatgpt'when a custom provider is configured and it doesn't use OpenAI auth (i.e.requires_openai_authis false). The method should always returnauth_method: Noneifrequires_openai_authis false.The same bug also causes the NUX (new user experience) screen to be displayed in the VSCE in this situation.