Issue with git authentication in VSCode based IDEs

[matifali]

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:

{
  "git.useIntegratedAskPass": false,
  "github.gitAuthentication": false
}

This ensures that Git authentication works correctly for Cursor IDE users.

Possible Solution(s)

This can be done in 2 ways,

1. Modify the CLI to apply the specified settings for Cursor when configuring Git authentication.
   

   coder/cli/gitauth/vscode.go

   Lines 31 to 34 in 92870f0

   	// code-server's default configuration path.
   	filepath.Join(xdg.DataHome, "code-server", "Machine", "settings.json"),
   	// vscode-remote's default configuration path.
   	filepath.Join(home, ".vscode-server", "data", "Machine", "settings.json"),

2. Use a 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.