Hi, Felix from Anthropic here. I work on Claude Cowork and Claude Code.<p>Claude Cowork uses the Claude Code agent harness running inside a Linux VM (with additional sandboxing, network controls, and filesystem mounts). We run that through Apple's virtualization framework or Microsoft's Host Compute System. This buys us three things we like a lot:<p>(1) A computer for Claude to write software in, because so many user problems can be solved really well by first writing custom-tailored scripts against whatever task you throw at it. We'd like that computer to not be _your_ computer so that Claude is free to configure it in the moment.<p>(2) Hard guarantees at the boundary: Other sandboxing solutions exist, but for a few reasons, none of them satisfy as much and allow us to make similarly sound guarantees about what Claude will be able to do and not to.<p>(3) As a product of 1+2, more safety for non-technical users. If you're reading this, you're probably equipped to evaluate whether or not a particular script or command is safe to run - but most humans aren't, and even the ones who are so often experience "approval fatigue". Not having to ask for approval is valuable.<p>It's a real trade-off though and I'm thankful for any feedback, including this one. We're reading all the comments and have some ideas on how to maybe make this better - for people who don't want to use Cowork at all, who don't want it inside a VM, or who just want a little bit more control. Thank you!
FWIW I think many of us would actually very much love to have an official (or semi official) Claude sandboxing container image base / vm base. I wonder if you all have considered making something like the cowork vm available for that?
There is this:<p><a href="https://code.claude.com/docs/en/devcontainer" rel="nofollow">https://code.claude.com/docs/en/devcontainer</a><p>It does work but I found pretty quickly that I wanted to base my robot sandbox on an image tailored for the project and not the other way around.
Perhaps useful, I discovered: <a href="https://github.com/agent-infra/sandbox" rel="nofollow">https://github.com/agent-infra/sandbox</a><p>> All-in-One Sandbox for AI Agents that combines Browser, Shell, File, MCP and VSCode Server in a single Docker container.
This? <a href="https://code.claude.com/docs/en/devcontainer" rel="nofollow">https://code.claude.com/docs/en/devcontainer</a>
what would you use it for?
Not OP, but having the exact VM spec your agent runs on is useful for testing. I want to make sure my code works perfectly on any ephemeral environments an agent uses for tasks, because otherwise the agent might invent some sort of degenerate build and then review against that. Seen it happen many times on Codex web.
Claude Cowork grabs local DNS resolution on macOS which conflicts with secure web gateway aka ZTNA aka SASE products such as Cloudflare Warp which do similar. The work-around is to close Cowork, let Warp grab mDNSResponder's attention first, then restart Claude Desktop, or some similar special ordering sequence. It's annoying, but you could say that about everything having to do with MITM middleboxes.
I think these are are excellent points, but the complaint talks about significant performance and power issues.
Felix, is there any way you guys could fix this simple, but absolutely terribly annoying bug?<p>Claude mangles XML files with <name> as an XML Tag to <n><p><a href="https://news.ycombinator.com/item?id=47113548">https://news.ycombinator.com/item?id=47113548</a>
I would look at how podman for Mac manages this; it is more transparent about what's happening and why it needs a VM. It also lets you control more about how the VM is executed.
I tried to use it right after launch from within Claude Desktop, on a Mac VM running within UTM, and got cryptoc messages about Apple virtualization framework.<p>That made me realize it wants to also run a Apple virtualization VM but can’t since it’s inside one already - imo the error messaging here could be better, or considering that it already is in a VM, it could perhaps bypass the vm altogether. Because right now I still never got to try cowork because of this error.
I accidentally clicked the Claude Cowork button inside the Claude desktop app. I never used it. I didn't notice anything at the time, but a week later I discovered the huge VM file on my disk.<p>It would be really nice to ask the user, “Are you sure you want to use Cowork, it will download and install a huge VM on your disk.”
Same. I work on M3 Pro with 512GB disk, and most of the time I have aroung 50GB free that goes down to 1GB often quite quick (I work with video editing and photos and caches are agressive there). I use apps like Pretty Clean and some own scripts (for brew clean, deleting Flutter builds, etc). So every 10GB used is a big deal for me.<p>Also discovered that VM image eating 10GB for no reason. I have Claude Desktop installed, but almost never use it (mostly Claude Code).
Jesus Christ what kind of potatos are you using when 10 GB of disk space are even noticable for you?
Can you allow placing the VM on an external disk?<p>Also, please allow Cowork to work on directories outside the homedir!
Any chance you guys could get the Claude Desktop installer fixed on Windows? It currently requires users to turn on "developer mode."<p>Sorry for the ask here, but unaware of other avenues of support as the tickets on the Claude Code repo keep getting closed, as it is not a CC issue.<p><a href="https://github.com/anthropics/claude-code/issues/26457https://github.com/anthropics/claude-code/issues/26457" rel="nofollow">https://github.com/anthropics/claude-code/issues/26457https:...</a>
Do you think it would be possible in the future to maybe add developer settings to enable or disable certain features, or to switch to other sandboxing methods that are more lightweight like Apple seatbelt for example?
It would be really nice to have an option to not do this since a ton of companies deny VMs in their group policies.
To a firm with such policies, to allow Cowork <i>outside</i> the VM should be strictly worse.<p>Ironically, VMs are typically blocked because the infosec team isn't sure how to look inside them and watch you, unlike containers where whatever's running is right there in the `ps` list.<p>They don't look inside the JVM or .exes either, but they don't think about that the same way. If they treat an app like an exe like a VM, <i>and the VM is as bounded as an app or an exe, with what's inside staying inside</i>, they can get over concerns. (If not, build them a VM with their sensors inside it as well, and move on.)<p>This conversation can take a while, and several packs of whiteboard markers.
Agreed. Need to make this a choice for us.
There's a lot that's not being said in (2). That warrants more extensive justification, especially with the issues presented in the parent post.
They're using the harnesses provided by the respective underlying Operating Systems to do virtualization.<p>I'd like to explore that topic more too, but I feel like the context of "we deferred to MacOS/Windows" is highly relevant context here. I'd even argue that should be the default position and that "extensive justification" is required to NOT do that.
> <i>real trade-off … thankful for any feedback</i><p>Speaking as a tiny but regulated SMB that's dabbling in skill plugins with Cowork: we strongly appreciate and support this stance. We hope you don't relax your standards, and need you not to. We strongly agree with (1), (2), and (3).<p>If working outside the sandbox becomes available, Cowork becomes a more interesting exfil vector. A vbox should also be able to be made <i>non</i>-optional — even if MDM allows users to elevate privileges.<p>We've noticed you're making other interesting infosec tradeoffs too. Your M365 connector aggressively avoids enumeration, which we figured was intentional as a seatbelt for keeping looky-loos in their lane.* Caring about foot-guns goes a long way in giving a sense of you being responsible. Makes it feel less irresponsible to wade in.<p>In the 'thankful for feedback' spirit, here's a concrete UX gap: we agree approval fatigue matters, and we appreciate your team working to minimize prompts.<p>But the converse is, when a user rejects a prompt — or it ends up behind a window — there's no clear way to re-trigger. Claude app can silently fail or run forever when it can't spin up the workspace, wasn't allowed to install Python, or was told it can't read M365 data.<p>Employees who've paid attention to their cyber training (reasonably!) click "No" and then they're stuck without diagnostics or breadcrumbs.<p>For a CLI example of this done well, see `m365-cli`'s `auth` and `doctor` commands. The tool supports both interactive and script modes through config (backed by a setup wizard):<p><a href="https://pnp.github.io/cli-microsoft365/cmd/cli/cli-doctor/" rel="nofollow">https://pnp.github.io/cli-microsoft365/cmd/cli/cli-doctor/</a><p>Similarly, first party MCPs may run but be invisible to Cowork. Show it its own logs and it says "OK, yes, that works but I still can't see it, maybe just copy and paste your context for now." A doctor tool could send the user to a help page or tell them how to reinstall.<p>Minimal diagnostics for managed machines — running without local admin but able to be elevated if needed — would go a long way for the SMBs that <i>want</i> to deploy this responsibly.<p>Maybe a resync perms button or Settings or Help Menu item that calls cowork's own doctor cli when invoked?<p>---<p>* When given IDs, the connector can read anything the user can anyway. We're able to do everything we need, just had to ship ID signposts in our skill plugin that taps your connector. Preferred that hack over a third party MCP or CLI, thanks to the responsibility you look to be iteratively improving.
> (2) Hard guarantees at the boundary: Other sandboxing solutions exist, but for a few reasons, none of them satisfy as much and allow us to make similarly sound guarantees about what Claude will be able to do and not to.<p>This is the most interesting requirement.<p>So <i>all</i> the sandbox solutions that were recently developed all over GitHub, fell short of your expectations?<p>This is half surprising since many people were using AI to solve the sandboxing issue have claimed to have done so over several months and the best we have is Apple containers.<p>What were the few reasons? Surely there has to be some strict requirement for that everyone else is missing.<p>But still having a 10 GB claude.vmbundle doesn't make any sense.
Cowork has been an insane productivity boost, it is actually amazing. Thank you!
[dead]
It's incredible how many applications abuse disk access.<p>In a similar fashion, Apple Podcasts app decided to download 120GB of podcasts for random reason and never deleted them. It even showed up as "System Data" and made me look for external drive solutions.
The system data issue on macOS is awful.<p>I use my MacBook for a mix of dev work and music production and between docker, music libraries, update caches and the like it’s not weird for me to have to go for a fresh install once every year or two.<p>Once that gets filled up, it’s pretty much impossible to understand where the giant block of memory is.
Yep, it <i>is</i> an awful situation. I'm increasingly becoming frustrated with how Apple keeps disrespecting users.<p>I downloaded several MacOS installers, not for the MacBook I use, but intending to use them to create a partitioned USB installer (they were for macOS versions that I could clearly not even use for my current MacBook). Then, after creating the USB, since I was short of space, I deleted the installers, including from the trash.<p>Weirdly, I did not reclaim any space; I wondered why. After scratching my head for a while, I asked an LLM, which directed me to check the system snapshots. I had previously disabled time machine backup and snapshots, and yet I saw these huge system snapshots containing the files I had deleted, and kicker was, there was no way to delete them!<p>Again I scratched my head for a while for a solution other than wiping the MacBook and re-installing MacOS, and then I had the idea to just restart. Lo and behold, the snapshots were gone after restarting. I was relieved, but also pretty pissed off at Apple.
It's just as bas on Windows. Operating Systems and Applications have been using the user's hard drive as a trash dumping ground for decades. Temporary files, logs, caches, caches of caches, settings files, metadata files (desktop.ini, .fseventsd, .Trashes, .Spotlight-V100, .DS_Store). Developers just dump their shit all over your disk as if it belongs to them. I really think apps should have to ask permission before they can write to files, outside of direct user-initiated command.
I can't help but think back to a conversation with my girlfriend in 1984. She had just bought a PC and I had bought a Mac.<p>She said "Oh, you bought a toy computer. How cute!"<p>I've owned every architecture of Mac since then, and I still think of it is my toy computer.
Disk utility lets you delete them.
Because Apple differentiates their products by their storage sizes, they also sell iCloud subscription. There is zero (in fact negative) incentive to respect your storage space.
I had the same problem and had some luck cleaning things up by enabling "calculate all sizes" in Finder, which will show you the total directory size, and makes it a bit easier to look for where the big stuff is hiding. You'll also want to make sure to look through hidden directories like ~/Library; I found a bunch of Docker-related stuff in there which turned out to be where a lot of my disk space went.<p>You can enable "calculate all sizes" in Finder with Cmd+J. I think it only works in list view however.
I’d recommend GrandPerspective:[1] it’s really good at displaying this sort of thing, has been around for over two decades, and the developer has managed to keep it to <5MB which is perfect when you’re running very low on space.<p>[1] <a href="https://grandperspectiv.sourceforge.net/" rel="nofollow">https://grandperspectiv.sourceforge.net/</a>
Something like <a href="https://dev.yorhel.nl/ncdu" rel="nofollow">https://dev.yorhel.nl/ncdu</a> with ("brew install ncdu") is great if you are okay with the command line. It's very annoying to drill down in the Finder especially if it's hidden directories.
Also DaisyDisk! Beautiful app. Perfect for discovering this kind of thing.
A ton of thanks. This "hack" allowed to finally see some stuff that was eating up a lot of my space and was showing up as "System Data". It turned out the Podman virtual machine on my MacBook had eaten up more 100GB!
You can also just use du -hs, eg. to show the size of all subdirectories under ~/Library/Caches/ do:<p><pre><code> du -hs ~/Library/Caches/*</code></pre>
The trick is to reboot into recovery partition, disable SIP, then run OmniDiskSweeper <i>as root</i> (as in `sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper`). Then you can find all kinds of caches that are otherwise hidden by SIP.
Even worse on ipad. My wife is an artist and 100gigs of "system data" is completely inscrutable and there's zero ways to fix it besides a full wipe.
Seconding.<p>I should not have to hack through /Libary files to regain data on a TB drive because Osx wanted to put 200gbs of crap there in an opaque manner and not give the user ANY direct way to regain their space.
I simply run GrandPerspective (GUI app, <a href="https://grandperspectiv.sourceforge.net/" rel="nofollow">https://grandperspectiv.sourceforge.net/</a>), or dust (terminal app, <a href="https://github.com/bootandy/dust" rel="nofollow">https://github.com/bootandy/dust</a>), to give me an idea of what is going on with disk usage.
Equally egregious are applications that insist on using the primary disk to cache model data/sample data/whatever
My 256gb Mac Mini currently has 65gb of "System Data" and 40gb of "MacOS"
Gotta hit that docker system prune -a
> Once that gets filled up, it’s pretty much impossible to understand where the giant block of memory is.<p>Your friend is called ncdu and can be used as follows:<p><pre><code> sudo ncdu -x -e --exclude Volumes /System/Volumes/Data/
</code></pre>
The exclude for Volumes is necessary because otherwise ncdu ends up in an infinite loop - "/Volumes/Macintosh\ HD/Volumes/" can be repeated ad nauseam and ncdu's -x flag doesn't catch that for whatever reason.
Don't run "du -h ~/Library/Messages" then, I've mentioned that many times before and it's crazy to me to think that Apple is just using up 100GB on my machine, just because I enable iMessage syncing and don't want to delete old conversations.<p>One would think that's a extremely common use case and it will only grow the more years iMessage exists. Just offload them to the cloud, charge me for it if you want but every other free message service that exists has no problem doing that.
<p><pre><code> sudo du -sh ~/Library/Messages
Password:
du: /Users/cvaske/Library/Messages: Operation not permitted
</code></pre>
Wow, SIP is a bit more insidious than I remember. Maybe I should try it in Terminal.app rather than a third party app... I wonder if there will ever be a way to tell the OS "this action really was initiated by the user, not malware, let them try to do what they say they want to do"<p>Edit: investigating a bit more, apparently the lack of a sudo-equivalent, an "elevate this one process temporarily" command is intentional in the design, so that malicious scripts can't take advantage of that "this is really the user" approval path. I can't say I agree with that design decision, but at least it's an ethos.
Offloading to the cloud and charging the user seems like a bigger breach of expectations than the hard drive space.
Same with photos. You can enable the option to offload but there’s no way to control how much is used locally. I don’t know why messages does that either. Also no easy way to remove the hundreds of thousands of photos in messages across all chats.
Agreed, it should work like the iCloud Photos library; cache locally, but pull from the cloud when necessary.
Even with the way Photos work - which is desirable, I agree - I should be able to specify a limit on how much local disk it uses.<p>I don't know what the formula it uses is, but it's insufficient.
There is a workaround… You can create an APFS partition on your main drive, set it to a fixed size (e.g. 10GB), and then move the location of your Photos library to that drive.<p><i>Note that if your Photos library is already larger than you want it to be, you may need to make sure it's synced, delete it, and create a new library on the drive. It will then sync with iCloud. But that's a hassle, and I would back up the library before you do this.</i>
System Settings > General > Storage. Click the ⓘ next to Messages. Sort by size and delete large attachments.
Appreciate the suggestion but that's similar to fixes like "Have you tried re-installing your OS, maybe that fixes the issue?".<p>I don't want to babysit my attachments or delete old conversations just because Apple doesn't put effort into that app. Probably my fault for still using it, but Telegram, WhatApp and Signal all manage to do it better.
This one drives me nuts. Not just on Mac, also on iPhone/iPad. It's 2026, and 5G is the killer feature advertised everywhere. There's no reason to default to downloading gigabytes of audio files if they could be streamed with no issue whatsoever.
I'm on 5G right now and it just struggled to load the HN front page due to local network congestion. At times of day when it's not congested it reaches 60-90Mbyte/s in the same physical location<p>Spotify just gave up while trying to show me my podcasts. I can't listen to anything not already downloaded right now.<p>Yet at 3am I'll be able to download a 100GB LLM without difficulty onto the same device that can't stream a podcast right now.<p>Unfortunately I don't think 5G is the streaming panacea you have in mind. Maybe one day...
Only reason I still download from Apple Music to device is for lossless and hi-res lossless, which would otherwise use a lot of cellular data.
On 5G, it depends. There are still plenty of people around the world who don't have unlimited data plans.
I had the same problem but with a bad time machine backup. ~300GB of my 512GB disk, just labeled the generic "System Data". I lost a day of work over it because I couldn't do Xcode builds and had to do a deep dive into what was going on.
This seems to be a recent popular tool to handle this - <a href="https://github.com/tw93/Mole" rel="nofollow">https://github.com/tw93/Mole</a><p>I also prompt warp/gemini cli to identify unnecessary cache and similar data and delete them
> Apple Podcasts app decided to download 120GB<p>That's one way to drive sales for higher priced SSDs in Apple products. I'm pretty sure that that sort of move shows up as a real blip on Apple's books.
Suprisingly Claude is amazing at cleaning up your macbook. Tried, works like a charm.
Someone actually still uses the built-in podcasts app?
Not sure what you have against it. Works great for me. No subscription required. And if I do want to pay for ad free shows and support creators it's easy to do so.<p>Use whatever you like but I don't think Podcast app users are rare by any stretch of the imagination.
It's absolutely fine, from what I can tell
AFAIK the native Podcast app for iPhone is the only way to make PC-phone podcast file syncing work. This stops you downloading the same podcast file twice, once on your PC and once on your phone.
It probably has more active users than all third party podcast apps on all mobile platforms combined. The power of defaults.
It's generally a good app. People in the tech community like Overcast, but I've always found its UI completely illogical. Apple Podcasts is organized like I'd expect a podcast app to be.
My WinSxS folder is 17Gb
I guess it could warn about it but the VM sandbox is the best part of Cowork. The sandbox itself is necessary to balance the power you get with generating code (that's hidden-to-user) with the security you need for non-technical users. I'd go even further and make user grant host filesystem access only to specific folders, and warn about anything with write access: can think of lots of easy-to-use UIs for this.
The vibe coding giveth and the the vibe coding taketh away, blessed be the vibe coding
Arguably, even without LLM, you too should be dev-ing inside a VM...<p><a href="https://developer.hashicorp.com/vagrant" rel="nofollow">https://developer.hashicorp.com/vagrant</a> is still a thing.<p>The market for Cowork is normals, getting to tap into a executive assistant who can code. Pros are running their consumer "claws" on a separate Mac Mini. Normals aren't going to do that, and offices aren't going to provision two machines to everyone.<p>The VM is an obvious answer for this early stage of scaled-up research into collaborative computing.
Yeah, very easy to do today. May VPS providers help with this, checkout:<p><a href="https://exe.dev" rel="nofollow">https://exe.dev</a><p><a href="https://sprites.dev" rel="nofollow">https://sprites.dev</a><p><a href="https://shellbox.dev" rel="nofollow">https://shellbox.dev</a>
Yes! Whether VPS or local VM, this is a thing for good reasons.<p>Some reasons aren't even optional. Small but regulated entities exist, and most "Team" sized businesses aren't in Google apps or "the cloud" as they think about it, but <i>are</i> in M365, and do pay for cyber insurance.<p>Cowork with skills plugins that leverage Python or bash is a remarkably enabling framework given how straightforward it is. A skill engineer can sit with an individual contributor domain expert, conversationally decompose the expert's toil into skills and subcommands, iterate a few times, and like magic the IC gets hours back a day.<p><i>Cowork is Agents-On-Rails™ for LLM apps, like Rails was to PHP for web apps.</i><p>The VM makes that anti-fragile.<p>For any SaaS builders reading this: by far most white collar small business work is in Microsoft Office. The scarce "Continue with Microsoft" OIDC reaches more potential SMB desks than the ubiquitous "Continue with Google" and you don't have to learn the legacy SAML dance.<p>Anthropic seems to understand this. It's refreshing when a firm discovers how to cater to the 25–150 seat market. There's an uncanny valley between early adopters and enterprise contracts, but the world runs on SMBs.<p>Sign them <i>all</i> up!
I prefer devcontainers for more involved project setups as they keep it lighter than introducing a VM. It’s also pretty easy to work with Docker (on your host) with the docker-outside-of-docker feature.<p>However, I’m also curious about using NixOS for dev environments. I think there’s untapped potential there.
we love nix for dev environments, and highly recommend it. many other problems go away. don't see that as what's being solved here, though.<p>containers contain stuff the way an open bookcase contains books, they're just namespaces and cgroups on a file system overlay, more or less, held together by willpower not boundaries:<p><a href="https://jvns.ca/blog/2016/10/10/what-even-is-a-container/" rel="nofollow">https://jvns.ca/blog/2016/10/10/what-even-is-a-container/</a><p><a href="https://github.com/p8952/bocker" rel="nofollow">https://github.com/p8952/bocker</a><p>as a firm required to care about infosec, we appreciate the stance in their (2). and MacOS VMs are so fast now, they might as well be containers except, you know, they work. (if not fast, that should be fixed.)<p>that said, yes, running local minikube and the like remain incredibly useful for mocking container envs where the whole environment is inside a machine(s) boundary. containers are _almost_ as awesome as bookcases…
I concur. I don't want to install libraries on my host machine that I won't use for anything other than development, e.g., Node.js.<p>On macOS, Lima has been a godsend. I have Claude Code in an image, and I just mount the directory I want the VM to have access to. It works flawlessly and has been a replacement for Vagrant for me for some time. Though, I owe a lot to Vagrant. It was a lifesaver for me back in the day.
I believe that employees in Anthropocs use CC to develop CC now.<p>AI really give much user ability to develop a completed product, but the quality is decreasing. Professional developers will be in demand when the products/features become popular.<p>First batch of users of new products need to take more responsibility to test the product like a rats in lab
> AI really give much user ability to develop a completed product, but the quality is decreasing. Professional developers will be in demand when the products/features become popular.<p>Looking at the amount of issues, outages and rookie mistakes the employees are making leads me to believe that most of them are below junior level.<p>If anyone were to re-interview everyone at Anthropic for their own roles with their own interview questions, I would guess that >75% of them would not pass their own interviews.<p>The only team the would pass them are the Bun team and some other of the recently acquired startups.
I literally spent the last 30 mins with DaisyDisk cleaning up stuff in my laptop, I feel HN is reading my mind :)<p>I also noticed this 10GB VM from CoWork. And was also surprised at just how much space various things seem to use for no particular reason. There doesn't seem to be any sort of cleanup process in most apps that actually slims down their storage, judging by all the cruft.<p>Even Xcode. The command line tools installs and keeps around SDKs for a bunch of different OS's, even though I haven't launched Xcode in months. Or it keeps a copy of the iOS simulator even though I haven't launched one in over a year.
> Xcode…keeps around SDKs for a bunch of different OS's<p>Not a new problem, unfortunately. DevCleaner is commonly used to keep it under control: <a href="https://github.com/vashpan/xcode-dev-cleaner" rel="nofollow">https://github.com/vashpan/xcode-dev-cleaner</a>
Is there no crond and find on MacOSX ?
Yup it uses Apple Virtualization framework for virtualization. It makes it so I can't use the Claude Cowork within my VMs and that's when I found out it was running a VM, because it caused a nested VM error. All it does is limit functionality, add extra space and cause lag. A better sandbox environment would be Apple seatbelt, which is what OpenAI uses, but even that isn't perfect: <a href="https://news.ycombinator.com/item?id=44283454">https://news.ycombinator.com/item?id=44283454</a>
I don’t have an opinion on how they should handle the nested VMs probably, but I very much disagree that Seatbelt is better. Claude Code (aka `claude`) uses it, and it’s barely good for anything.<p>Out of curiosity, why are you running Cowork inside a VM in the first place? What does that get you that letting Cowork use its own VM wouldn’t?
seatbelt is largely undocumented.
OpenAI Codex CLI was able to use it effectively, so at least AI knows how to use it. Still, its deprecated and not maintained, Apple needs to make something new soon.
just ask AI to document it
As much as an inconvenience this may be, this is exactly what "agents" should be doing. If your tool doesn't have a builtin sandbox that is intended to be used at all times, you're using something downright hazardous and WILL end up suffering data loss.
On a similar tangent, but on the opposite end of the spectrum, check out this month-old discussion on HN: <a href="https://news.ycombinator.com/item?id=46772003">https://news.ycombinator.com/item?id=46772003</a><p>ChatGPT's code execution container contains 56 vCPUs!! Back then, simonw mentioned:<p>> It appears to have 4GB of RAM and 56 (!?) CPU cores <a href="https://chatgpt.com/share/6977e1f8-0f94-8006-9973-e9fab6d24418" rel="nofollow">https://chatgpt.com/share/6977e1f8-0f94-8006-9973-e9fab6d244...</a><p>I'm seeing something similar on a free account too: <a href="https://chatgpt.com/share/69a5bbc8-7110-8005-8622-682d5943dcd9" rel="nofollow">https://chatgpt.com/share/69a5bbc8-7110-8005-8622-682d5943dc...</a><p>On my paid account, I was able to verify this. I was also able to get a CPU-bound workload running on all cores. Interestingly, it was not able to fully saturate them, though - despite trying for 20-odd minutes. I asked it to test with stress-ng, but it looks like it had no outbound connectivity to install the tool: <a href="https://chatgpt.com/share/69a5c698-28bc-8005-96b6-9c089b0cc561" rel="nofollow">https://chatgpt.com/share/69a5c698-28bc-8005-96b6-9c089b0cc5...</a><p>Anyways, that's a lot of compute. Not quite sure why its necessary for a plus account. Would love to get some thoughts on this?
I imagined someone at Anthropic prompted "improve app performance", and this was the result.
A better UX would be to prompt the user, asking "Would you like to use the app in a sandbox for enhanced safety?" and only then download the Ubuntu linux image used in the VM
Same thing on Windows. The VM bundle is at %AppData%\Claude\vm_bundles
Ok, so a lot of this boils down to the fact that this sort of software really wants to be running on linux. For both windows and mac, the only way to (really) do that is creating a VM.<p>It seems to me that the main issue here is painful disconnects between the VM and the host system. The kernel in the VM wants to manage memory and disk usage and that management ultimately means the host needs to grant the guest OS large blocks of disk and memory.<p>Is anyone thinking about or working on narrowing that requirement? Like, I may want the 99% of what a VM does, but I really want my host system to ultimately manage both memory and disk. I'd love it if in the linux VM I had a bridge for file IO which interacted directly with the host file system and a bridge in the memory management system which ultimately called the host system's memory allocation API directly and disabled the kernels memory management system.<p>containers and cgroups are basically how linux does this. But that's a pretty big surface area that I doubt any non-linux system could adopt.
Given that Claude Code runs without issues on macOS, I'd guess that it's more about sandboxing shell sessions (i.e. not macOS applications or single processes, for which solutions exist).<p>Unfortunately, unlike Linux, macOS doesn't have a great out-of-the-box story there; even Apple's first-party OCI runtime is based on per-container Linux VMs.
I think only BSD really has a good sandboxing solution beside linux (jails).<p>And after looking into Jails, it looks like BSD also supports linux cgroups... that's actually really impressive. [1]<p>[1] <a href="https://docs.freebsd.org/en/books/handbook/linuxemu/#linuxemu" rel="nofollow">https://docs.freebsd.org/en/books/handbook/linuxemu/#linuxem...</a>
The upgrade to the native installer gave me some issues, I had Claude fail to return any responses and continuously eat memory until my computer crashed! The only fix I could figure out is nuking my entire .claude dir, losing all my history etc with it
It’s a solved problem in the VM world too. Memory ballooning is a technique where a driver inside the VM kernel cooperates with the hypervisor to return memory back to the host by appearing to consume the memory from the VM. And disk access is even easier; just present a network filesystem to the VM.
The network file system to host is usually pretty slow no? That was my impression.<p>As for memory ballooning, the main issue with it is that it (generally) only gets triggered when the host runs out of memory.<p>For a host which is only running VMs, this is fine. But for the typical consumer host it becomes cumbersome as you still need to give the VM a giant memory block and hope that your VM of choice is good enough to free on time. It's also uncoordinated. When swapping needs to happen, if the VM was using the host for allocation the host could much more efficiently decide what needs to go into swap.<p>And if the host was in charge of both the memory and file system, then things like a system cache could be done more efficiently on top of all that.
Sure it uses a few GB just like everything else these days, but some of the comments also mention it being slow?
I see this as a feature. The cost of isolation
macbook pro m4 bought last year. worked on so many codes and projects. never hot after closing lid. installed electron claude. closed lid and went to sleep and woke up to macbook that has been hot all night. uninstall claude. problem went away.<p>i kept telling myself this BUT NEVER ELECTRON AGAIN.
To be fair, ChatGPT seems to be a native app and still somehow managed to continuously burn some 30-40% of CPU on my mac that ended up being attributable to some shimmer animation for two never-loading icons.
I don't know if Electron is the issue here, my Wintel machine has Claude Code running 24/7 and doesn't ever heat up.<p>Might be virtualization woes or something adjacent.
It’s not electron
The macOS Claude app is absolutely an electron app, which is what the github issue in this post is about.<p>If you'd like to verify for yourself: On your mac, right click on the Claude app icon and click on "Show Package Contents" and then navigate to Contents > Frameworks > Electron Framework.framework.
Yes it certainly is.
> woke up to macbook that has been hot all night<p>this is usual reason for divorce /s
I really love Anthropic's models, but, every single product/feature I've used other than the Claude Code CLI has been terrible... The CLI just "sticked" for me and I've never needed (or arguably looked in depth) any other features. This for my professional dayjob.<p>For personal use, where I have a Pro subscription and adventure into exploring all the other features/products they have... I mean, the experience outside of Claude Code and the terminal has been... bad.
> every single product/feature I've used other than the Claude Code CLI has been terrible<p>yeah they're shipping too fast and everything is buggy as shit<p>- fork conversation button doesn't even work anymore in vscode extension<p>- sometimes when I reconnect to my remote SSH in VSCode, previously loaded chats become inaccessible. The chats are still there in the .jsonl files but for some reason the CC extension becomes incapable of reading them.
I tend to agree here. Today, I tried to get the claude chat to give me a list of Jira tickets from one board (link provided) and then upload it to notion with some additional context. It glitched out after trying the prompt over again 4x. I eventually gave up and went back to the terminal.
Yes. This is my experience as well. The software quality is generally horrible. It surely has improved a lot over the last couple of months, but it is still pretty horrible.<p>It is quite normal for me to have to force-close Claude Desktop.
Aren't most these people recommending random tools in the github chat for this entry just attempting to exploit naive users? Why would anyone in this day and age follow advice of new users to download new repos or click at random websites when they already attempt to use claude code or cowork?
While I generally agree with your sentiment, these tools aren't bad ones:<p>- Santa is a very common tool used by macOS admins to lock down binary and file access privileges for apps, usually on managed machines<p>- Disk Inventory X and GrandPerspective are well-known disk space usage tools for macOS (I personally use DaisyDisk but that requires a license)<p>- WizTree and WinDirStat are very common tools from Windows admin toolkits<p>The only one here I can say is potentially suspect is ClearDisk. I haven't used it before, but it does appear to be useful for specifically tracking down developer caches that eat up disk space.
Way slower, but way better than chat mode. Nothing beats Claude Code CLI imo.
Yeah, that's why I do not install these tools on my personal devices anymore and instead play with them on a VPS.<p>Try this if you have claude code -- ls -a your home dir and see all the garbage claude creates.
Mac Problems...<p>so crazy on a windows desktop I at most complain if it is hardcoded to the system drive (looking at you ollama)
This GitHub issue itself is clearly AI slop. If you’ve been dealing with GitHub issues in the past months it will be obvious, but it’s confirmed at the end:<p>> Filed via Claude Code<p>I assume part of it is true, but determining which part is true is the hard part. I’ve lost a lot of time chasing AI-written bug reports that were actually something else wrong with the user’s computer. I’m assuming the claims of “75% faster” and other numbers are just AI junk, but at least someone could verify if the 10GB VM exists.
If your codebase is entirely vibe coded, I feel it only appropriate to permit issues being vibed as well. It's hypocritical otherwise.
Use an agent to summarize and generate reproducers for each report, another to select issues to be fixed in the next iteration, a third one to implement changes, a fourth for code review...
I wouldn't think it's inappropriate for an AI agent to file an issue against another AI agent, which itself is largely written by AI.
Hey, they did admit that they vibed this in a week and released it to everyone.
That seems somewhat reasonable.<p>Storage should be cheaper, complain about Apple making you pay a premium.
Its just another example and just a detail in the broader story: We cannot trust any model provider with any tooling or other non model layer on our machines or our servers. No browsers, no cli, no apps no whatever. There may not be alternatives to frontier models yet, but everything else we need to own as true open source trustable layer that works in our interest. This is the battle we can win.
What's funny is interacting with it in claude code. Claude-desktop-cowork can't do anything about the VM. It creates this 10 GiB VM, but the disk image starts off with something like 6-7 GiB full already, which means any of the cowork stuff you try to do has to fit into the remaining couple of gigs. It's possible to fill it up, and then claude cowork <i>stops working</i>. Because the disk is full. Claude cowork isn't able to fix this problem. It can't even run basic shell commands in the VM, and Opus4.6 is able to tell the user that, but isn't smart enough/empowered to do anything about it.<p>So contrary to the github issue, my problem is that it's not <i>enough</i> space. So the fix is to navigate to ~/Library/Application\ Support/Claude/vm_bundles, and then ask Claude Code to upsize the disk to a sparse 60 GiB file, giving cowork much more space to work in while not immediately taking up 60 GiB.<p>Bigger picture, what this teaches me though, is that my knowledge is still useful in guiding the AI to be able to do things, so I'm not obsolete yet!
This is exactly the kind of issues we will see more and more frequently with vibe-coding.
The amount of bad things this companies software does is staggering. The models are amazing, the code sucks.
Are we sure that this isn't a sparse image? It will report as the full size in finder, but it won't actually be consuming that much space if it's a sparse image
Just write a Claude OS already.
All code in Claude™ is written by Claude™
Also apparently eating 2 GB RAM or so to run an entire virtual machine even if you've disabled Cowork. Not sure which of this is worse. Absolute garbage.
The software seems to get into more and more and communicate about what it's doing less and less. That's the crux.<p>Pondering...
Noodling...
Some other nonsense...
labelled "high priority" a month ago. No actual activity by Anthropic despite it being their repo. I'm starting to get the feeling they're not actually very good at this?
[dead]
[dead]