You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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"
This issue is consistent and reappears each single time. Here is the output log:
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:
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"
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
The text was updated successfully, but these errors were encountered: