# 开发者用Cursor云代理实现全自动修Bug

- 来源：eric zakariasson (@ericzakariasson)
- 发布时间：2026-07-31 23:00
- AIHOT 分数：59
- AIHOT 链接：https://aihot.virxact.com/items/cms93ji4u02x2ro9km43nhbvl
- 原文链接：https://x.com/ericzakariasson/status/2083206179254309036

## AI 摘要

Eric Zakariasson分享了一个让用户反馈自动变成修复方案的工作流：应用内反馈进入PostHog，Cursor云代理结合会话回放、事件和错误数据循环调试，验证通过后自动创建带测试的GitHub PR，他只需在手机上审核。该模式还可扩展用于自动分类重复问题、分析UX缺陷等场景。

## 正文

i've been building some smaller apps over the last weeks for myself， friends and family and discovered a pretty nice pattern in the process

you see， after building， i'm not particularly interested in fixing bugs or triaging feature requests. i just want to get the job done

so i've set up a system that lets me and other users fix bugs and build features without me having to actually open cursor

the flow：
1. someone files feedback in the app
2. it lands in posthog with the submitted text， session replay， events， and errors
3. a cursor cloud agent picks it up with that context， plus live read-only posthog mcp
4. it loops until the fix is verified， then opens a github pr with tests
5. i get a ping and review it on my phone

we give our cloud agents access to all the necessary user context， and they'll figure it out

with this in place， we can start setting up more abstractions in between. if we're getting a high volume， we might want to triage first with another cloud agent or some automation. the feedback can create a github or linear issue， which we later pick up with a cron-backed cloud agent that decides which are duplicates. there are so many ways to configure this， you just gotta try it out and see what works for you

but there's so much more here that is untapped. with session replays and event logs， you can have a cloud agent look at each session replay to extract ux pitfalls and improvement areas. you can have another agent looking at event logs to see weird patterns. another one for errors or similar

try it out and see what you can do！