Preflight Checklist
- I person searched existing requests and this characteristic hasn't been requested yet
- This is simply a azygous characteristic petition (not aggregate features)
Problem Statement
Every perpetrate connection and PR explanation created by Claude Code automatically includes a convention URL astatine the bottommost (e.g. https://claude.ai/code/session_...). There is nary opt-in prompt, nary warning, and nary mention of it during onboarding. Users only observe it aft it's already polluting their git history.
Proposed Solution
Make the convention URL attribution opt-in — don't see it unless the personification explicitly enables it. A one-time punctual during onboarding ("Would you for illustration to see a nexus backmost to this Claude convention successful perpetrate messages?") would beryllium the perfect UX.
Alternative Solutions
-
Keep it opt-out but make the mounting discoverable — show it during first perpetrate pinch a "Don't adhd this again" option
-
Remove it wholly and trust only connected the existing Co-Authored-By: Claude trailer for attribution
Priority
Medium - Would beryllium very helpful
Feature Category
Other
Use Case Example
A developer uses Claude Code to build a feature, commits the work, and opens a PR.
Their teammates and unfastened root contributors spot https://claude.ai/code/session_... astatine the bottommost of each perpetrate and PR description.
It looks unprofessional, clutters history, and the developer had nary thought it was being added.
Additional Context
- The attribution.commit: "" mounting successful .claude/settings.json tin suppress it, but it's wholly undiscovered
- A commit-msg git hook tin besides portion it, but it doesn't ever occurrence reliably successful remote/cloud environments
English (US) · 
Indonesian (ID) · 
