Adding "Copilot" menu for users who already uninstalled Copilot is deeply offensive
Long ago, I installed VS Code, and there was a "Copilot" extension. I uninstalled it immediately. I do not want to use Copilot, I do not want Copilot on my computer, I do not want to use software that is capable of integrating with Copilot. I want that trash completely off my computer. Yet today I opened VSCode¹ and found a new menu:  After poking around, I discovered I could disable it with a new checkbox.  But that is not good enough for me. There are two problems here: 1. Those of us who have already uninstalled Copilot have already said no to Copilot. **We should not have to say no again.** This is the worst thing about Microsoft software these days— having to disable the same features over, and over, and over, as VPs get more desperate to juice metrics and software updates re-enable things we've already disabled. The checkbox should have been off by default for people who don't have the chatbot plugin installed, and for new users uninstalling the plugin should automatically uninstall the Copilot extension. You should respect our consent. Respect our humanity. 2. Although I've disabled the Copilot menu, I am unsatisfied because my copy of VS Code *still contains the Copilot menu code*. Previously I could remove all Copilot code completely by simply uninstalling the Copilot extension. Now,
Posted by mcclure on Jan 13, 2025, 5:10 PM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
Adding "Copilot" menu for users who already uninstalled Copilot is deeply offensive
Long ago, I installed VS Code, and there was a "Copilot" extension. I uninstalled it immediately. I do not want to use Copilot, I do not want Copilot on my computer, I do not want to use software that is capable of integrating with Copilot. I want that trash completely off my computer. Yet today I opened VSCode¹ and found a new menu:  After poking around, I discovered I could disable it with a new checkbox.  But that is not good enough for me. There are two problems here: 1. Those of us who have already uninstalled Copilot have already said no to Copilot. **We should not have to say no again.** This is the worst thing about Microsoft software these days— having to disable the same features over, and over, and over, as VPs get more desperate to juice metrics and software updates re-enable things we've already disabled. The checkbox should have been off by default for people who don't have the chatbot plugin installed, and for new users uninstalling the plugin should automatically uninstall the Copilot extension. You should respect our consent. Respect our humanity. 2. Although I've disabled the Copilot menu, I am unsatisfied because my copy of VS Code *still contains the Copilot menu code*. Previously I could remove all Copilot code completely by simply uninstalling the Copilot extension. Now,
Comments (0)
No comments yet. Start the discussion.