Cursor[old]

Cursor

 
Cursor is one of the most popular coding agents. However, it still lacks some critical features that would allow it to be widely deployed and governed by enterprises. More specifically, additional steps are required to ensure that Lumia, in its various configurations, can effectively govern Cursor.
 
The following tables summarize the additional steps required to complement the Lumia deployment/integration in order to fully govern Cursor:
ã…¤
Zscaler
Cloudflare
Netskope
Local installers
Cursor IDE
-
1
1
3
cursor-agent (CLI) *
2
2
2
-
(*) Deep inspection for cursor-agent is currently only partially supported.
 
[1] Some enterprise proxies don’t support HTTP/2 bidirectional streaming, so Cursor IDE must be configured to use HTTP/1.1.
This can be done by applying the following setting in settings.json:
{
		...
		"cursor.general.disableHttp2": true
}
On macOS, this settings file is located at ~/Library/Application Support/Cursor/User/ , and on Windows at %APPDATA%\Cursor\User\.
 
[2] Some enterprise proxies don’t support HTTP/2 bidirectional streaming, so Cursor CLI must be configured to use HTTP/1.1.
This can be done by applying the following setting in cli-config.json:
{
		...
		"network": {
				"useHttp1ForAgent": true
		}
}
On macOS, this settings file is located at ~/.cursor/ , and on Windows at %USERPROFILE%\.cursor\. See here for additional information on the config file and details about this setting.
 
[3] If Cursor is already running, it needs to be restarted to activate Lumia governance, since Cursor loads the PAC definitions on startup.
 
 
 
Â