Git commands - terrible experience after last updates

[mirtch]

Describe the Bug

Since last few updates commiting or any git command really is a slug for vibe coders. Every git command ends with

~
~
~
~
~
~
~
~
~
~
(END)

and agent is stuck there in pager forever. All you can do is press skip… only option. And then agent doesn’t understand why user cancelled task.

I don’t even get it why git commands aren’t automatically run by agents in this IDE. Yes I know i can set up a profile myself and basically bash git save but I would prefer to have it being done automatically at certain steps in my workflow by my agent without me doing it.

Steps to Reproduce

When an agent git (anything) it can’t go through

Expected Behavior

Agent should move on after each completed command and a commit shouldn’t take more than a few seconds, now it takes forever if you can manage to pull it off.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.6 (user setup)
VSCode Version: 1.99.3
Commit: 68b8fe7396ea37d8acdaaaa08ba316ba359a4160
Date: 2025-07-30T18:17:09.810Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

[condor (Condor (Tee))]

hi @mirtch and welcome to Cursor Forum.

It seems that the Agent was running interactive commands which require use actions. This depends on the Git command and options used.

You can ask Agent to “Remember that interactive commands can not be run in terminal as they block, always make sure to run non-interactive commands only”.

[toupee09 (Toupee)]

This keeps happening on one of my Windows machines and it is so incredibly frustrating. I have no idea how to fix it. Sometimes it works fine and other times it just doesn’t - often for hours. And I end up burning tokens because I need to cancel and re-prompt. ■■■■■.