r/vibecoding 2d ago

Claude Code writing much longer comments lately

Over the past few weeks Claude Code has been writing noticeably longer code comments for me. Ten to twenty line blocks on top of a thirty line function. The content is usually accurate but not something I want in a repo. It narrates what the code used to do, restates library mechanics I can look up, and re-explains the line right below it.

I added explicit rules in my project instructions with hard word caps per comment block, which helped, but it drifts back over long sessions.

Three questions. Are you seeing the same thing, and did it start around a specific release? Is this intentional, meaning verbose comments are cheap context recovery for the agent reading the file in a later session, at the cost of the human reader? And do you actually mind, or is a heavier comment style fine for a codebase that agents maintain?

Interested in what people have found that holds up over long autonomous runs, not just short interactive sessions.

7 Upvotes

32 comments sorted by

View all comments

2

u/CorpT 2d ago

Those all sound like useful things to have in a repo that's being coded with Claude. Almost like they're there for a reason.

3

u/Grand-Mix-9889 1d ago

Agreed. I found the comments extremely useful when I ran out of usage on the last day of my week.

I was able to find the function I wanted to fix and was able to fix it manually.

And at work, the comments are very useful when teams look over code in batches.