Extension version: 1.48.2 (codeium.codeium)
After the Windsurf → Devin Desktop rebrand on June 2nd 2026, the VS Code extension login flow is completely broken. Clicking Login opens the browser successfully, the Google OAuth completes, but instead of redirecting back to VS Code and completing the login, the browser lands on an empty page with this URL:
devin://acp?connectorId=devin-cloud
VS Code never receives the auth callback and the extension stays stuck in the login loop indefinitely. The "Signing in to Auth... (Cancel for manual token sign in)" notification spins forever.
Steps to reproduce:
Install codeium.codeium extension v1.48.2 in VS Code
Click "Windsurf: Login" from the status bar
Complete Google OAuth in browser
Browser lands on devin://acp?connectorId=devin-cloud — empty page
VS Code never gets authenticated
What I tried:
Restarting VS Code and machine
Switching from Brave to Chrome
Running VS Code as administrator
Setting codeium.detectProxy: false
Creating a new Devin account
Expected behavior: After OAuth completes in browser, VS Code receives the callback and extension shows as logged in.
Suspected cause: The rebrand changed the OAuth redirect URI from the Codeium/Windsurf auth endpoint to the Devin Cloud ACP connector, which is the wrong flow for the VS Code extension login.
Extension version: 1.48.2 (codeium.codeium)
After the Windsurf → Devin Desktop rebrand on June 2nd 2026, the VS Code extension login flow is completely broken. Clicking Login opens the browser successfully, the Google OAuth completes, but instead of redirecting back to VS Code and completing the login, the browser lands on an empty page with this URL:
devin://acp?connectorId=devin-cloud
VS Code never receives the auth callback and the extension stays stuck in the login loop indefinitely. The "Signing in to Auth... (Cancel for manual token sign in)" notification spins forever.
Steps to reproduce:
Install codeium.codeium extension v1.48.2 in VS Code
Click "Windsurf: Login" from the status bar
Complete Google OAuth in browser
Browser lands on devin://acp?connectorId=devin-cloud — empty page
VS Code never gets authenticated
What I tried:
Restarting VS Code and machine
Switching from Brave to Chrome
Running VS Code as administrator
Setting codeium.detectProxy: false
Creating a new Devin account
Expected behavior: After OAuth completes in browser, VS Code receives the callback and extension shows as logged in.
Suspected cause: The rebrand changed the OAuth redirect URI from the Codeium/Windsurf auth endpoint to the Devin Cloud ACP connector, which is the wrong flow for the VS Code extension login.