他跑通了“用户反馈→云代理修bug→自动开PR”的流程，你只用在手机审查。适合不想手动修bug的人。
作者分享了用PostHog收集用户反馈文本、会话回放和错误日志的工作流。Cursor Cloud Agent借助只读的PostHog MCP获取上下文，循环验证修复后自动创建带测试的GitHub PR。他建议用云代理分析会话回放和事件日志来发现UX问题，再用cron任务对高量反馈去重。
i've been building some smaller apps over the last weeks for myself, friends and family and discover...
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! 💬 9 🔄 3 ❤️ 57 👀 2309 📊 24 ⚡