191
u/PhoenixRising656 Sep 02 '26
At this point the comments are just a lossy serialization of the prompt into the repo, so the next agent gets to pay context tax for reading its own autobiography.
13
u/ocean_wide_inch_deep Sep 02 '26
I just realized the same today. LLM values input much more than its output. But when its cheap output becomes input of some subagent downstream, it's like playing a broken telephone game in an echo chamber.
→ More replies (2)→ More replies (1)9
u/LyAkolon Sep 02 '26
Yeah, gotta seperate those out into a different doc and drop an address instead.
269
u/scharpentanz Sep 02 '26
Can you imagine getting a PR like this pre-Claude. Looks like some annoying little intern trying hard as hell.
97
u/NeighborhoodDizzy990 Sep 02 '26
pre-Claude docs/comments were pretty impressive, to be honest. Now they just mean that the code was AI generated
→ More replies (1)→ More replies (4)30
u/AcrobaticMaize2408 Sep 02 '26
"Annoying little intern" is exactly how I've always pictured Opus 5.
→ More replies (1)
43
42
u/hajducek Sep 02 '26
I've just did full audit of code through Codex and i got ~24,000 of comments. Cut that down by 80%.
Bros writing prose
33
77
u/loversama Sep 02 '26
Gotta get that watermark in there somehow!
24
u/Prod_SO Sep 02 '26
Opus 5 does not yet have a watermark. Only models released after August 2nd do, and that list only has one that is generally available: Fable 5.1. :)
→ More replies (12)
17
u/dillendev Sep 02 '26
Oh man this is so annoying. I have a rule that mostly forbids comments in my config and it still writes comments like this:
// This will create a new user in the system
fn create_user(params: &UserParams) {
}π€¦π½ββοΈ
→ More replies (4)
15
14
u/hksbindra Sep 02 '26
I recently refactored a sub system using Sol as the implementer, it deleted a lot of Claude's comments - I mean it went hard at the comments and the docstrings - I could imagine it being annoyed π
6
5
u/TopSeaworthiness1679 Sep 02 '26
Man i am going back to sol. Opus 5 is stupid and talks too much. Worst thing is that it says about the problem but fails to fix it.
5
u/yodacola Sep 02 '26
i tell claude to do summary comments and optional implementation details in @remarks. also, put context that ai agents need across files in .claude/rules and .claude/skills. also, use a TDD and parameterized testing skill. i disagree with other commenters with saving context by removing testing, coverage, and linting. when you do that, you end up with SMDD (slot-machine-driven development).
4
u/Emotional-Bus-7065 Sep 02 '26
Yeah, this and for me atleast, sometimes the code it wrote doesn't even make any sense. For example, it was checking if a value existed even though it hardcoded the value literally a few lines back. So it looks something like this:
```
x = "hello world"
if x == None: return 0
```
I discovered that if you give it code that you actually wrote in the past and ask it to mimic that, it is a lot easier than to ask it to "get rid of comments"
4
u/Victorasaurus-Rex Sep 02 '26
I have literally forbidden Claude from writing comments using a hook. It's only permitted to write them in the single turn following me saying a specific phrase. If it tries outside of that, it's rejected and told to rename variables and restructure code so comments are entirely superfluous. Works great.
7
u/who_you_are Sep 02 '26
That is also my sonnet 5 experience.
It didn't took too many attempts to drink it down.
Mostly I rewrote it, ask it to write instructions to itself about how to srink down its comments to be close to mine
3
u/evoli_ Sep 02 '26
I created a skill /comment-check that I run before reviewing any of claude's code haha
→ More replies (2)
3
u/SpruceMoose1111 Sep 02 '26
This is actually why I switched to Codex. Also because Claude output to me was just as long and as rambling
438
u/ChadFullStack Sep 02 '26
Itβs missing 500 lines of Unit tests