This GitHub issue itself is clearly AI slop. If you’ve been dealing with GitHub issues in the past months it will be obvious, but it’s confirmed at the end:

> Filed via Claude Code

I assume part of it is true, but determining which part is true is the hard part. I’ve lost a lot of time chasing AI-written bug reports that were actually something else wrong with the user’s computer. I’m assuming the claims of “75% faster” and other numbers are just AI junk, but at least someone could verify if the 10GB VM exists.

▲

16bitvoid 3 hours ago | parent | next [-]

If your codebase is entirely vibe coded, I feel it only appropriate to permit issues being vibed as well. It's hypocritical otherwise.

	▲	rzzzt 43 minutes ago \| parent [-]
		Use an agent to summarize and generate reproducers for each report, another to select issues to be fixed in the next iteration, a third one to implement changes, a fourth for code review...

▲

chuckadams 4 hours ago | parent | prev [-]

I wouldn't think it's inappropriate for an AI agent to file an issue against another AI agent, which itself is largely written by AI.