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

Cody stops working within 5 minutes after sign in or opening VS code #6941

Open
Giuleus957 opened this issue Feb 4, 2025 · 2 comments
Open
Assignees
Labels
bug Something isn't working repo/cody

Comments

@Giuleus957
Copy link

Giuleus957 commented Feb 4, 2025

Version

Cody 1.64.0 , VS Code 1.96.4

Describe the bug

Every time I open VS code or that i sign in again in my account everything works but after about 5 minutes (or sometimes less) everything stops working and i need to exit and reopen VS code or sign in again in with my github account for it to work again. The issue consists in:

  • Model selector in the chat disappearing

Image

  • being unable to interact with the chat anymore (i can send the prompt but without any response)

  • "Edit code" feature gives me the following error message: "This feature has been disabled by your Sourcegraph site admin"

Image

This issue is consistent and reappears each single time. Here is the output log:

cody_log.txt

A shorter log i have just produced in which it gave the issue quite quickly (i cut the following part where i am signing in again):

cody_log_shorter.txt

Even though after the re-connection to the github account now it's more stable. However, this is an issue i have had recurrently for the last month.

Expected behavior

Cody should be able to stay connected consistently and be able to use its chat and edit code feature for as long as I am using VS code

Additional context

I have the same issue across two different windows laptops

@Giuleus957 Giuleus957 added bug Something isn't working repo/cody labels Feb 4, 2025
Copy link

linear bot commented Feb 4, 2025

@PriNova
Copy link
Collaborator

PriNova commented Feb 4, 2025

Hey @Giuleus957

Thank you for opening this issue report. We are working on a fix.

Sorry for the inconvenience.

@PriNova PriNova self-assigned this Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working repo/cody
Projects
None yet
Development

No branches or pull requests

2 participants