fix: account dropdown not refreshed when switching users on the same …#323
Merged
Conversation
…deployment via URI When two Coder URIs targeting the same deployment URL but different users are opened in sequence, the account dropdown in the plugin header would still show the username from the first session instead of updating to reflect the newly authenticated user. This happened because the same-URL URI handling path calls refreshSession() directly, bypassing the onConnect callback that normally updates the account dropdown label after a successful connection. While refreshSession() correctly replaced the REST client and CLI instances with ones authenticated as the new user, it never propagated that change to the UI. The fix updates refreshSession() to also refresh the account dropdown label and visibility immediately after the new client is initialized, keeping the UI consistent with the active session. - resolves DEVEX-372 - resolves DEVEX-374
zenithwolf1000
approved these changes
Jun 22, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…deployment via URI
When two Coder URIs targeting the same deployment URL but different users are opened in sequence, the account dropdown in the plugin header would still show the username from the first session instead of updating to reflect the newly authenticated user.
This happened because the same-URL URI handling path calls refreshSession() directly, bypassing the onConnect callback that normally updates the account dropdown label after a successful connection. While refreshSession() correctly replaced the REST client and CLI instances with ones authenticated as the new user, it never propagated that change to the UI.
The fix updates refreshSession() to also refresh the account dropdown label and visibility immediately after the new client is initialized, keeping the UI consistent with the active session.