Agent Connectivity Issues

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Aftere yesterday’s update to v2.4.21, agents are failing on most external connections. Such as try to git push or executing AWS CLI commands.

Resolve network connectivity to AWS services (SSM Parameter Store, STS, Lambda, Cognito) in us-east-2. Once connectivity is restored, the tests should pass as the infrastructure is deployed and configured correctly.

Steps to Reproduce

Ask the agent to git push.

Expected Behavior

Asks for confirmation that I want to push. And on confirmation, automatically push to the repo. This is typically followed up with a summary of the work done.

Operating System

Windows 10/11

Version Information

Version: 2.4.21 (Universal)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Auto. Problem seems independent of choice.

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. This is a known issue in version 2.4.21. A few users are seeing the same thing after updating.

A similar case is discussed here: Terminal problems when used by agent

On macOS, Cursor tries to launch bin/zsh instead of /bin/zsh. On Windows, there are PATH issues in the agent-exec extension (spawn git ENOENT, ERR_INVALID_ARG_TYPE). The agent can’t run commands correctly.

For now, the workaround is:

  • Roll back to version 2.3.34 (stable and worked without these issues): Download · Cursor
  • Or check Developer Tools (Help > Toggle Developer Tools) when the agent tries to run a command. You might see more error details there.

The team is aware. If you want to help with debugging, please share what you see in the Developer Tools Console when the agent tries to do git push.

1 Like