Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Continue extension login stuck on 'Signing in to Continue' even after browser authentication #4516

Open
2 of 3 tasks
Jackpkn opened this issue Mar 6, 2025 · 3 comments
Open
2 of 3 tasks
Assignees
Labels
ide:vscode Relates specifically to VS Code extension kind:bug Indicates an unexpected problem or unintended behavior priority:highest Indicates the highest possible priority

Comments

@Jackpkn
Copy link

Jackpkn commented Mar 6, 2025

Before submitting your bug report

Relevant environment info

- OS: Debian 12
- Continue version: 1.0.2
- IDE version: 1.98.0
- Model:
- config:
  

  
  OR link to assistant in Continue hub:

Description

After clicking 'Get Started' in the Continue extension, the login process redirects me to a browser where I choose a free trial. After selecting it, I am redirected to the 'Create your first assistant' page. However, even after completing this step, the Continue extension in VS Code remains stuck on 'Signing in to Continue' instead of recognizing the successful login. This suggests that the extension is not handling authentication properly

Image

Image

To reproduce

  1. Install and open the Continue extension in VS Code.
  2. Click Get Started, which redirects to the browser login page.
  3. Choose a free trial or login option.
  4. After completing login, the browser redirects to the 'Create your first assistant' page.
  5. Meanwhile, the Continue extension in VS Code still shows 'Signing in to Continue', even though the login should be completed.

Log output

@dosubot dosubot bot added ide:vscode Relates specifically to VS Code extension kind:bug Indicates an unexpected problem or unintended behavior labels Mar 6, 2025
@tomasz-stefaniak tomasz-stefaniak added priority:highest Indicates the highest possible priority and removed "needs-triage" labels Mar 10, 2025
@vladimirsvicevicsrb
Copy link

Samo issue when choosing "Use your API keys" option...

@tomasz-stefaniak
Copy link
Collaborator

@vladimirsvicevicsrb we recently published a fix for this. The problem was that we made the Anthropic API key optional on the client but the server still expected it to be provided. That said, If you are still experiencing this issue, do you mind sharing your console logs or network logs if anything (like a failed request) stands out there?

@mucio-at-untitled-data-company

same here, In the Output tab in VSCode there is nothing logged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ide:vscode Relates specifically to VS Code extension kind:bug Indicates an unexpected problem or unintended behavior priority:highest Indicates the highest possible priority
Projects
None yet
Development

No branches or pull requests

4 participants