[MODEL] Move version-controlled files with `git mv`, not plain mv

Preflight Checklist

• [x] I have searched existing issues for similar behavior reports
• [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Other unexpected behavior

What You Asked Claude to Do

move a source file from directory A to directory B

What Claude Actually Did

Uses plain OS move file operation, effectively deletes it in directory B and starting a new file with no history in directory B.

Expected Behavior

use version control system's move operation, preserving history.

Files Affected

commits in .git

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

1. Create a new local git project with directory A containing file foo.sh. Contents of the file don't really matter.
2. Ask Claude to create directory B and move foo.sh into it.
3. Run git status and see that, as far as Git is concerned, foo was not moved. Instead, the old foo.sh was deleted and the new one was created at the new location. All the history of the old foo.sh is gone with it.

Claude Model

Sonnet

Relevant Conversation

Impact

High - Significant unwanted changes

Claude Code Version

v2.0.22

Platform

Anthropic API

Additional Context

_No response_