Right now, the current creator flow involves authenticating within the SDK window in Unity for every project independently, including username, password and MFA each time. This creates friction for creators that may work on dozens or hundreds of projects on a regular basis, where if they rebuild their computer, upgrade or have any number of things happen, the SDK signs them out and they have to reauthenticate their user again.

The Creator Companion already connects to the project when it is open to perform actions such as package management and other tasks. I propose moving the authentication to one of two places:

1) Move to a browser-based OAUTH like method, where the unity client would open the user's default browser, authenticate in a fashion like Canny does (SSO with VRC credentials), and then the browser kick's that authenticated session back to Unity. Using this method would not reduce the number of authentication attempts, but would reduce friction by using the existing login session within the browser.

2) Move the authentication process to the Creator Companion itself, and leverage the connection already made by the VCC and the SDK to manage authentication between projects. I.e. You download and install the VCC, and it has you sign in, and then it could handle keeping the unity projects authenticated when it is running. Using this method in the way I am thinking would reduce the number of authentication requests from a user by N-1, where N is the number of projects.

Let me know if there is any more details. I thought of this while stupid drunk and ranting about VCC with friends... I'm sure I should have taken notes... lol