-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Add --user to copilot argument #3169
Copy link
Copy link
Open
Labels
area:authenticationLogin, OAuth, device auth, token management, and keychain integrationLogin, OAuth, device auth, token management, and keychain integrationarea:configurationConfig files, instruction files, settings, and environment variablesConfig files, instruction files, settings, and environment variables
Description
Metadata
Metadata
Assignees
Labels
area:authenticationLogin, OAuth, device auth, token management, and keychain integrationLogin, OAuth, device auth, token management, and keychain integrationarea:configurationConfig files, instruction files, settings, and environment variablesConfig files, instruction files, settings, and environment variables
Type
Fields
Give feedbackNo fields configured for Feature.
Describe the feature or problem you'd like to solve
I'd like to be able to specify which user I want to use for the session as I have both work and personal accounts
Proposed solution
If you have a script that puts in all the startup values you like by default, would be nice to have an ability to also specify the user/account that the session should start up in. Kind of annoying to have to later specify the user via
/user.Example prompts or workflows
I have a powershell alias
csthat launches copilot with a few args like--yoloand a few other fields. I'd like to also be able to pass a flag like-Personalor-Workto force it to use a specific account for the new session (so I don't forget and spend personal on work or vice versa). Just relying on the last one launched gets tricky because sometimes I forget and in the morning when I get to work and I forget to switch back to work account.Additional context
No response