The AI Ping-Pong: When Every Reply Is a ChatGPT Screenshot

A Hacker News thread with 104 points and 48 comments captures a growing developer frustration: being inundated with AI-generated responses that are context-free, often wrong, and forwarded by people who clearly haven't read them.
What's happening
The original poster (theorchid) describes three incidents:
- Found malware on GitHub, asked an AI for advice — got nothing useful. Opened a GitHub discussion. First reply: the exact same text the AI had given them. Called it out, comment deleted. Second reply: same AI response again.
- Asked a business owner a question at work. Got a ChatGPT screenshot back. Replied that it was wrong. A minute later: another ChatGPT screenshot. The owner never read either answer.
- Got a Reddit DM, replied, went back and forth. After a few messages realized it was an AI agent.
Other developers pile on with similar stories. programmertote recounts: “Last week, my boss, Chief Data and Analytics Officer, dumped an AI-generated proposal (~7 pages) on how to structure semantic layer on top of our dbt models. As the Data Engineering lead, I had to read it and found a few glaring issues… Yesterday, one of my coworkers shared another obviously AI-generated 5-page draft of an SOP on how to reintegrate old metrics. I think we will all become AI-output-reviewers eventually.”
jadar wonders if we’ll soon be forced to execute on AI output instead of sharing it: “If you can reason yourself into a working system, you know what you’re talking about. If not, then it’s not worth taking the time to figure it out.”
Practical responses
- jochem9: “Ask them to share their prompt instead. Calls them out on their AI bs and gives a way forward to share what they actually thought.”
- LPisGood: “Why not ask your AI to review their AI slop? That which can be sent without thought can be responded to without thought.”
- sixtyj envisions automated replies: “This text was automatically generated and has not been reviewed before being sent. It’s AI garbage and I refuse to read it. Do it again. And do it better.”
Takeaway for devs
Blindly forwarding AI output erodes trust and creates busywork for reviewers. Setting a norm — share the prompt, reason about the output, or risk being ignored — could slow the AI ping-pong. As one commenter put it: establish a consensus that distributing unread AI slop is not acceptable.
📖 Read the full source: HN AI Agents
👀 See Also

Two AI Failures in One Demo: Claude Code Fixes Spelling Instead of Schema Error, OpenAI Mangles Custom Field Mapping
During a live workshop, Claude Code ignored a JSON schema validation error to fix spelling warnings, and OpenAI returned garbage on first attempt at mapping weird custom Salesforce fields.

Navigating the OpenClaw 2026.2.6-3 and OpenRouter Integration Issue
Users of OpenClaw 2026.2.6-3 paired with OpenRouter face persistent '401 User not found' errors. Join the community discussion as they explore solutions and share troubleshooting tips.

AI Agents Are Killing Code Review — The Principal-Agent Problem Explained
Inserting AI agents into the traditional code review process doubles review load, collapses trust signals, and creates an unsustainable imbalance — this is the principal-agent problem as applied to software engineering.

MiMo-V2.5-Pro Benchmarked: Strong Social Deduction Reasoning, Good Value vs K2.6
MiMo-V2.5-Pro competes with Kimi K2.6 in autonomous Blood on the Clocktower games, with a lopsided 88% Good / 48% Evil win rate, costs $0.99/game at 183k output tokens, and is practical with 2-3 hour matches.