includeCoAuthoredBy setting does not prevent hardcoded Claude Code attribution in commit messages

[shaneholloman]

Issue Description

The includeCoAuthoredBy: false setting in Claude Code settings.json does not prevent Claude Code from adding attribution to git commit messages. Claude Code still automatically adds:

Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

This appears to be hardcoded behavior that bypasses the configuration setting.

Expected Behavior

When includeCoAuthoredBy: false is set, no Claude Code attribution should be added to commit messages.

Actual Behavior

Claude Code adds attribution regardless of the setting value.

Configuration

{
  "includeCoAuthoredBy": false
}

Request

Need a deterministic way to completely disable all Claude Code attribution in git commits and pull requests.

[antenore]

I totally second this.

[antenore]

BTW, at the moment I'm using git hooks to deny some patterns in the commit messages, if anyone needs an example let me know

[mutech]

I go further, these attempts to sneak in advertising into other peoples work seems to be clearly illegal. Try hanging a poster with ads on somebodies wall...

This is even worse considering how AI attribution diminishes the credibility of code. I would not trust the next developer using AI to put as much effort into curating AI results as I do. These attributions constitute actual harm.

Antropic had to ask for consent, not assume it providing an opt-out that does not even work. This has a strong malicious scent to it: "What can they do about it? - Nothing, they're going to eventually just accept it"

[antenore]

See the official doc

https://docs.claude.com/en/docs/claude-code/settings

includeCoAuthoredBy is true by default, you can set it to false in the settings.

It works for me, so maybe is some settings precedences.

Edit: hit sent too quickly

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[mutech]

How much activity would it take for an issue to be fixed instead of ignoring it until it auto-closes?