Claude Desktop quietly spins up a 1.8GB VM on launch — with no off switch
Open the app to send one chat message and it boots a Hyper-V virtual machine. Users report it eating 12GB of disk for a Cowork sandbox they never enabled and can't remove. The AI company that sells craft, shipping a clunker.
The VM exists for Claude Cowork's sandbox. The complaint isn't that it exists — it's that it starts immediately, unconditionally, for chat-only use.
An engineer who runs his own agent harness explained the likely intent: warm the VM so responses feel instant. His version cools down after 10 minutes. Claude's doesn't.
The bug report, and what it's really about
The GitHub issue is short: Claude Desktop spawns a ~1.8 GB Hyper-V VM on every launch, even when you only want to chat. Other users piled on with worse numbers — "it took up 12gb on mine," and a Cowork bundle that "installs a ~10GB vm bundle which you cannot remove." The substance isn't the VM's existence — it's the lack of control.
A regular who builds the same kind of system explained the probable rationale, and why it's a defensible idea executed badly:
"this is probably a performance optimization for quick responses … My agent harness spins up a VM too, but it spins up on demand, cools down in 10 minutes and warms up when I focus back on the app. … People take more time to type a prompt than the VM takes to spin up." — gopalv
The contrast is the whole complaint: a warm sandbox is sensible; a sandbox you didn't ask for, can't disable, and can't delete is not. As one commenter clarified, the VM is for Claude Cowork's sandbox — "That doesn't help answer why they spin it up immediately and don't have a way to disable it though."
The craft critique lands hard because of who shipped it
The recurring jab was about reputation versus reality:
"So a company which has access to practically unlimited tokens and their best models makes crappy software. Huh who would've thought? /s" — pier25
A high-karma engineer attributed it to the obvious irony — that the app itself looks vibe-coded:
"Classic Anthropic, this comes across as LLM coded nonsense." — stuaxo
The most concrete evidence of rushed work came from a user who found platform-confused UI — on Windows, the Cowork permissions flow links to macOS system preferences:
"When you click the buttons for those permissions, it has broken links to macOS system preferences." — literatepeople
The control argument
Beyond the bug, the thread surfaced a broader grievance about software taking agency away from users:
"Back in the day, personalization / customization was all the rage … Now it's the opposite. It's about not letting user to have any control at all. … We are at the mercy of the machines." — zkmon
The fix is trivial, which is the point
This isn't a hard engineering problem — gate the VM behind first use of Cowork, add a toggle, let people uninstall the bundle. That it shipped without those is the tell the thread kept returning to: a company whose pitch is taste and capability shipped a desktop app that boots a multi-gigabyte VM to answer "what's the capital of France." The optimization instinct was right. The defaults were the failure.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
Google's DiffusionGemma writes a paragraph at once — 4x faster, and a bit dumber
Instead of one token at a time, it drafts a 256-token block and refines it in passes. Google says 1,000+ tokens/sec on an H100, at the cost of lower quality than regular Gemma. The thread's verdict: the speed changes how coding with a model feels.