Copilot Chat 模型选择透明度投诉：已选择 GPT-5.5 High，但实际会话质量与执行行为疑似存在未披露路由/降级

[sssm1990]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Actions

Body

你好，我需要投诉并请求 GitHub Copilot 团队解释 VS Code Copilot Chat 的模型选择透明度问题。

我在 VS Code Copilot Chat 中明确选择了 “GPT-5.5 · High” 模型档位，但在连续复杂代码任务中，实际表现出现明显异常，包括：

1. 执行质量与所选模型档位严重不匹配

   • 在同一任务中反复忽略已明确要求的工作方式。
   • 多次没有先读取已有实现，而是直接猜测参数。
   • 对同一问题反复叠加修复，随后又清理、撤回、再叠加，形成低质量循环。
   • 用户多次明确要求避免 fallback stacking、强制通过、表面覆盖式修复，但实际行为仍反复出现类似模式。

2. 模型身份与路由透明度不足

   • UI 显示我选择的是 “GPT-5.5 · High”。
   • 但 Copilot Chat 本身无法确认当前后端实际执行的是哪个模型版本。
   • Copilot Chat 也无法保证每一轮、每个工具调用、每个子步骤都使用所选模型。
   • 这导致用户无法判断 “GPT-5.5 · High” 是否是强制模型选择，还是仅仅是偏好/路由建议。

3. 缺少可审计信息

   • 我无法在界面中看到每一轮实际使用的 model id。
   • 我无法确认是否发生过后台降级、重试、子任务切换模型、容量路由或灰度实验。
   • 如果存在后台模型切换或降级，界面没有明确提示用户。

4. 具体问题影响

   • 我正在处理一个真实商业仓库中的 3ds Max 插件 UI 修复任务。
   • Copilot 多次没有按既有 Theme A 布局读取真实参数，而是根据截图猜测 Theme B 的布局数值。
   • 这导致修复反复引入新问题，例如按钮消失、底部控件不可见、布局高度错误等。
   • 用户不得不反复人工截图、指出问题、要求撤回错误方向，严重影响效率和信任。

我希望 GitHub/Copilot 团队明确回答以下问题：

1. VS Code 中选择 “GPT-5.5 · High” 后，是否保证整个会话固定使用该模型？
2. 如果不保证，在哪些情况下会发生后台路由、降级、重试或子任务模型切换？
3. 如果发生切换，为什么 UI 不提示用户？
4. 是否有日志字段可以显示每一轮实际使用的模型 ID？
5. 工具调用、代码编辑、摘要压缩、子代理任务是否可能使用不同模型？
6. 用户如何确认自己付费或选择的高等级模型实际被使用？
7. 是否可以提供一个透明的诊断导出方式，用于查看模型路由、降级、重试和失败信息？

我不是单纯反馈一次回答质量差，而是投诉产品层面缺乏透明度：用户选择了高等级模型，但实际运行链路无法被验证，也无法排除后台未提示的模型切换或降级。

请将此问题转交 GitHub Copilot / VS Code Copilot Chat 产品与工程团队，并提供正式解释。

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[v-ember]

Hi @sssm1990 , thanks for participating!

👋 and thank you for being a part of our community. To ensure a safe and supportive environment, we look to our Code of Conduct which states all communication here on the Community needs to be in English. Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting. We’ll be closing and locking any posts in languages other than English for now, including this one.