Make Opus 4.6 available for Copilot Pro+

[Mistralys]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot Agent Mode

Body

As a developer, I have subscribed to Copilot Pro+ specifically to get access to Claude Opus. However, only the Claude Opus 4.7 is currently available. Please also make Opus 4.6 available, even if it uses the same token multiplier.

Why? Because working with Opus 4.7 for the last few days, I have come to the frustrating conclusion that Opus 4.7 is really, really bad.

Since then I have confirmed this at work as well, where we have an enterprise account that enabled me to make direct comparisons between Opus 4.6 and 4.7. For example, it consistently goes off script with agent personas that worked really well with 4.5/4.6, to the point where comparing the output between the two is unrecognizable.

I am used to leveraging Claude Opus for the planning phase, letting Claude Sonnet do the actual work. However, my planner with Opus 4.7 persona just starts implementing things, which it has NEVER done with Opus 4.6. My Changelog Curator persona starts adding technical details to the changelog entries where the whole persona's philosophy is to leave out overly technical things like method or file names. Opus 4.7 just sprinkles those everywhere.

Looking online, it seems that to work as expected, Opus 4.7 needs its thinking to be set to xhigh. I don't see any thinking level for the model in VS Code Chat, so I wonder what it's set at.

TLDR; Opus 4.7 is completely useless for me in its current state, and will be an unfunny joke once it hits the planned 25x multiplier in June.

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

[Tony405-spec]

The issue isn’t capability, it’s loss of control:

Ignores persona constraints
Jumps into implementation instead of planning
Injects unnecessary technical detail

Workflows that relied on Opus (planning) → Sonnet (execution) are now unreliable. The same prompts that worked perfectly in 4.6 produce completely different, off-spec outputs in 4.7.

This breaks established prompt systems and adds friction instead of saving time.

Requests:

Bring back Opus 4.6 (even temporarily)
Add thinking level controls (e.g. xhigh) in VS Code
Improve persona adherence in Agent Mode

Right now, Opus 4.7 feels unpredictable less like a planner, more like an over-eager implementer.

[Mistralys]

Agreed. Opus 4.7 is bound to evolve or find niche uses, but right now you can't depend on it. Bringing back Opus 4.6 would be a good solution, and personally I would not mind it getting a reasonable multiplier for both sides.

We hear your feedback and want to make sure it is centralized in this discussion, which also may be updated if new information becomes available.

To keep conversations all in one place and to ensure you receive timely updates, we’ll be closing this post and recommend you repost your comment to the discussion linked above.