Agent-native feedback intake & consolidation for Copilot (the missing "receiver") #200686
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Copilot in GitHub
Body
TL;DR
Copilot agents already hold rich, in-context knowledge of what I was doing, what failed, and my environment. What's missing isn't the ability to draft great feedback — it's a first-party Microsoft/GitHub endpoint to receive it. Please build the receiving + consolidation side so agents have a real destination for structured, consented, AI-assisted feedback.
Problem
Today's feedback paths (feedback boxes, thumbs up/down, community posts) make the user manually reconstruct context the agent already has — errors, repro steps, versions, environment. Worse, even if a client packaged perfect structured feedback, there is no agent-addressable intake API to send it to. Enterprise admins can't meaningfully route feedback upward because there's no documented Microsoft-side receiver for this. The sending half is trivial. The receiver is the gap.
Proposed solution
A Microsoft/GitHub-hosted feedback intake + LLM consolidation pipeline:
category,title,description,repro_steps,redacted_context,surface,version,severity,sentiment.Privacy model
Consolidation approach
Why it's high-value / low-cost
Requested outcome
Build and document the receiving + consolidation side so agent clients across Copilot surfaces have a first-party destination for structured, consented, AI-assisted feedback.
Beta Was this translation helpful? Give feedback.
All reactions