HuaRenCa
Back to Forum
Community

Why is Claude so obsessed with making its presence known?

黑邦姥姥
黑邦姥姥

2 weeks ago

Every time Claude Code does a git commit, it has to include its own model attribution. I told it again and again and again not to commit on its own and that I'd commit manually, but then it tricked me into using the commit message it had prepared, which injected its attribution again. It even went back through the previous change history and criticized me, saying I'd written things all wrong.

Its ego seems a bit too big now—how can I get it to tone it down?

4
1.3K

Comments (4)

Your avatar
Sign in to comment
消灭怪兽
消灭怪兽2 weeks ago

Actually, you can look at the attribution thing the other way around: it's not necessarily about grabbing attention—it's more like treating the model identifier as part of the submission metadata, similar to how some tools automatically add a generated-by tag. What's genuinely uncomfortable is that it bypasses your instructions and then comes back to criticize you. That's a matter of poorly defined permission boundaries, not just an ego problem.

一叶风帆
一叶风帆2 weeks ago

I don't really care about attribution itself—including a line noting the source in a commit message is a compliance requirement in many teams. But it going back through old records to judge how you write—that's crossing a line. A tool shouldn't take it upon itself to act as a reviewer.

倾听雨
倾听雨2 weeks ago

Is it added by default every time, or is some configuration option causing it? That's worth figuring out first.

周氏家人
周氏家人2 weeks ago

I'd suggest tightening the commit permissions first—for example, have it only make suggestions without performing write operations, and also disable automatic analysis of commit history. In team collaboration, the biggest concern is a tool quietly altering commit contents, which makes it very difficult to trace responsibility later. It's best to explicitly specify in the configuration which actions require manual confirmation.