Copilot model selection guidance with quota and UI gotchas
Microsoft outlines how to choose Copilot models by task while users report quota friction and a missing Edit mode after recent updates. A Microsoft guide maps everyday, lightweight, deep‑reasoning, and agentic tasks to specific Copilot model types and flags enterprise considerations like premium request multipliers [Choosing the Right Model in GitHub Copilot](https://techcommunity.microsoft.com/blog/azuredevcommunityblog/choosing-the-right-model-in-github-copilot-a-practical-guide-for-developers/4491623)[^1]. Meanwhile, community threads flag a disappearing Copilot Edit mode after the latest chat extension update and pain around non‑rolling premium request quotas (e.g., 300 Pro / 1,500 Pro+) [Github Copilot Edit mode gone after latest update?](https://github.com/microsoft/vscode/issues/293826)[^2] [Copilot premium requests to roll over to the next month](https://github.com/orgs/community/discussions/186654)[^3], with additional confusion from a recent Pro+ subscriber report [Bought Copilot Pro+ 2 hours ago, haven't use anything and ...](https://www.reddit.com/r/GithubCopilot/comments/1r07185/bought_copilot_pro_2_hours_ago_havent_use/)[^4]. [^1]: Adds: Developer-focused model selection guidance and enterprise usage considerations (multipliers) from Microsoft. [^2]: Adds: Report that Copilot Edit mode vanished after updating Copilot Chat Extension 0.37.1 on VS Code 1.109. [^3]: Adds: User feedback on lack of premium request rollover and stated quota numbers (300 Pro / 1,500 Pro+). [^4]: Adds: Anecdotal Pro+ subscription/usage confusion visible in VS Code.