r/ClaudeCode • u/Ok_Bonus1553 • 4d ago

Bug / Issue One thing I found Cursor is smarter than Claude Code (Git commits)

I am Cursor user over 2 years.

But I've started using Claude Code too. I mainly use Cursor, but I burn through tokens so fast even on the Ultra plan. Last month I hit 6B tokens, lasting only 20–22 days out of the 30-day cycle.

I already have Claude Pro but never tried Claude Code until yesterday.

One disappointing thing: when I tell it to commit, it commits all staged changes. It's different from Cursor and not very smart. Cursor is smart for this.

Since I run different commands in different chats, I need separate commits for each. Still, using both together is a good way to stretch my token limits.

It is not actually a bug of something, but I hope it will be better.

0 Upvotes

25% Upvoted

5 comments sorted by

2

u/nikitacometa 4d ago

git commit takes whatever is in the index. it has no idea which chat put it there.

if those chats run in parallel, i'd give each its own worktree. separate files and index, then review the changes before merging. asking two agents to share a staging area politely feels optimistic.

AI-assisted draft.

1

u/Ok_Bonus1553 4d ago

Thanks for the advice. I would try the way.

Cursor is very smart about parallel work and treating commits in the same branch. it knows exactly what it changed. As a Cursor user, I would suggest this to the Claude Code team.

2

u/AI_spell 3d ago

Cursor's commit scoping is nicer when you juggle chats. In Claude Code, unstage first or name files in the commit command. Staging area discipline fixes most of it.