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
Currently, Coder has special handling for VSCode within the product that ensures proper Git authentication. However, this does not work for other VSCode-based IDEs like Cursor, which many customers now use extensively. As a result, developers using Cursor face Git authentication issues, especially when connected to remote workspaces for extended periods.
Desired Solution
Extend support to Cursor by modifying .cursor-server/data/Machine/settings.json with the necessary Git settings:
Problem Description
Currently, Coder has special handling for VSCode within the product that ensures proper Git authentication. However, this does not work for other VSCode-based IDEs like Cursor, which many customers now use extensively. As a result, developers using Cursor face Git authentication issues, especially when connected to remote workspaces for extended periods.
Desired Solution
Extend support to Cursor by modifying
.cursor-server/data/Machine/settings.json
with the necessary Git settings:This ensures that Git authentication works correctly for Cursor IDE users.
Possible Solution(s)
This can be done in 2 ways,
coder/cli/gitauth/vscode.go
Lines 31 to 34 in 92870f0
coder_script
to do the same in the cursor terraform module.Note
The same issue could exist for other VSCode-based IDEs, i.e., WindSurf, VSCodium, Theia IDE etc.
The text was updated successfully, but these errors were encountered: