Hacker News Reader

Comment by crooked-v | Hacker News Reader

Well, that explains the Github repo with 5000 issues, maybe about a third of which are random regressions of previous behavior.

View on HN

I snorted laughing at this. "We are experiencing tremendous growth" and it's just a codebase with 1,000 agents endlessly adding markdown documentation for every 1 line change.

I just learned that manually invoked skills MUST be the _first_ thing in the prompt, e.g. you can't have `disable-model-invocation: true` and say "Hi, /grill-me on X".

Worse, everything after the /grill-me is injected a second time into the prompt as a <command-args> so your prompt is literally added to the context TWICE. (first time in the original user prompt.)

I swear Anthropic is intentionally bloating your context so you burn tokens on useless bullshit like this.

Oh /loop was the crowning achievement. Basically guarantees you'll run a prompt at max context without caching over and over.

I have done exactly this as recently as yesterday, so I’m not sure why it doesn’t work for you.

To be clear: you can certainly do "Hi, /grill-me on X" anytime you want. You can even write "hi, /grill-me and use /search-docs", even though the /search-docs skill absolutely doesn't work. But the Claude Code _harness_ won't autoload the skill into context, so claude-the-model has to go "hmm, where can I find that skill, when I call the Skill tool with that name it no worky, so now I have to search the filesystem for that skill...".

https://github.com/anthropics/claude-code/issues/92769

The <command-args> I know because I just audited my raw Claude transcripts via ccglass. You can verify by just asking Haiku "hey, /grill-me does this skill autoload for you?" and then "/grill-me hey, how many times does this text appear in your context?"

You can trivially doublecheck me. The above prompts won't even eat 1% of a 5 hr on 20$ plan.

Okay, yes, I agree that that’s how it works. I thought when you said MUST you meant that it doesn’t work; it does work it’s just that it burns a turn or two to do the lookup there. I certainly agree it would be nice to not do so.

(And I didn’t know the double args thing, that’s very interesting! I should have said I only meant the first bit.)

Codex had over 15k issues last I checked including legit months old issues with the sandboxing/bubblewrap config.

Human contributions to issues, comments or submissions, were drowning in a sea of AI vomit. Tons of the issues had those AI issue submissions with the classic confidence of having identified the problem, but that smell I know a lot of us recognize of it not actually knowing what the problem is at all because it hadn't failed to fix it 5 times yet.

https://i.imgur.com/lYjn8xq.png

their claude code changelog 'fixed' % over time.

https://i.imgur.com/KJcem6c.png

I believe their peak month was >13k issues opened, but worth bearing in mind: "This issue has been automatically locked since it was closed and has not had any activity for 7 days.".

I was running into something similar where I had it working on a single Python file. Maybe part of the issue is that I had memory turned off, and the conversation might have spilled into two conversations. I wasn't using version control either, but since it was a single file with about 1000 lines of code, it didn't seem too hard to eventually get all of my features back.

Reply on news.ycombinator.com