claude-code - 💡(How to fix) Fix Commit message body repeatedly wraps at 72 chars despite explicit 100-char instruction [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45165Fetched 2026-04-09 08:11:47
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2closed ×1
RAW_BUFFERClick to expand / collapse

When asked to generate commit messages, Claude wraps body lines at ~72 characters even after being told (via memory/feedback) to wrap at 100. The rule is read and acknowledged each session, but the output still hard-wraps at the training default. This has been corrected multiple times across multiple sessions without sticking.

Expected: body lines wrap at 100 chars as instructed Actual: body lines wrap at ~72 chars (training default)

extent analysis

TL;DR

The issue can be addressed by re-evaluating how Claude's memory and feedback mechanisms are implemented to ensure that the wrap limit instruction is persisted across sessions.

Guidance

  • Review the session initialization code to ensure that the wrap limit instruction is correctly applied and persisted.
  • Verify that the feedback mechanism is properly updating Claude's configuration to reflect the new wrap limit.
  • Investigate the possibility of a default override or reset that occurs when a new session is started, causing the wrap limit to revert to its training default.
  • Check for any limitations or constraints in Claude's architecture that might prevent the wrap limit instruction from being applied consistently.

Notes

The issue suggests a potential discrepancy between the intended behavior and the actual implementation of Claude's memory and feedback mechanisms. Without more information about the specific implementation details, it is difficult to provide a more targeted solution.

Recommendation

Apply workaround: Implement a session-specific override to ensure that the wrap limit instruction is applied correctly for each session, as the root cause of the issue is likely related to how instructions are persisted across sessions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING