Don't be a meat proxy
摘要
作者抱怨人们把 AI 的完整输出直接转发到 Slack、PR 评论或群聊中，认为这种做法没有价值，因为接收者自己就能和 AI 对话，且更高效。他举例说明 AI 输出冗长、术语密集且可能包含看似合理但错误的胡话。建议先阅读、理解、验证 AI 输出，再用自己的话写回复，这样才算真正添加价值。在代码审查场景中，如果只是把任务描述和审查反馈复制粘贴给 Claude Code，那么实际做实现的是审查者，而提交者只是'肉代理'。
荐读理由
文章给出了明确可操作的做法：在收到AI输出后先阅读、理解、验证，再用自己的话转述，并指出在代码审查中避免当'肉代理'。这可以直接迁移到独立开发者与协作者或AI工具的日常交互中，减少无效沟通并提升代码审查质量。
原文
Don't be a meat proxy
Aug 03, 2026
Too often I ask a question in Slack or leave feedback under a merge/pull request or argue with friends in a WhatsApp group and get back:
Claude said: [giant response verbatim]
Please don't do this. I mean, I've done this. But I've been on the receiving end too many times now. This is not adding value. I can talk to Claude myself. It's going to be faster and I get to control the context. I don't need a meat proxy in between.
Reading AI output is extra effort. It's verbose, frequently contains all too plausible nonsense, and is increasingly jargon dense. I recently got this sentence from Claude:
NATS control-plane events: stream leader election / R3 quorum re-form during pod churn.
Jesus. I had to lookup almost every word to make sense of this.
By all means, prompt AI. But don't just relay the output. Read it, understand it, validate it, and then write a response in your own words (a decent certificate that you've done the prior steps). Making that effort is value you can add.
Take code review in particular. Shipping some code can be done with close to zero effort now: Copy/paste the ticket description into Claude Code. Don't look at the code or read what Claude has written. If there's any feedback from reviewers, copy/paste that into Claude Code as well. If necessary, iterate.
That works. But who has done the implementation? The reviewers did, using Claude Code, and you as a meat proxy.
这条对你有帮助吗？