Merged
Conversation
After `mux login`, the success message now includes the full path to the config file so users know exactly where their credentials are stored. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Summary
mux login, the success message now includes the full path to the config file (e.g.~/.config/mux/config.json) so users know exactly where their credentials were saved.getConfigPath(), so it respectsXDG_CONFIG_HOMEand works correctly across platforms.Before
After
Test plan
mux loginwith default config and verify the path is shownmux loginwithXDG_CONFIG_HOMEset and verify the custom path is shownmux login --name stagingand verify the environment name is correct🤖 Generated with Claude Code