As long as the VM closes when the application closes, I don’t see too much of an issue with this design decision.

It seems like the VM is a core part of how you use the application.

Apart from you have no idea what's going on in the VM. It's not as it has a virtual terminal. I'll play the skeptic archetype: What's not to say they're transmitting all prompts back HQ?

Don't be naive and don't think they don't already do this.

Why not ask itself and see what it says about it. "Claude, why are you running in a virtual machine and what are you doing?".

/shrug

	▲	Grombobulous 6 hours ago \| parent [-]
		Claude transmits all prompts back to HQ as a part of its basic functionality. If you are using an AI system to read your codebase from your local folder and make changes, whether or not you have a VM running or not is inconsequential. The Claude extension and/or CLI doesn’t need a VM to send code back to the mothership, you’re already running an executable program and granting it directory access. Whether you trust a company as a vendor is typically based on their privacy policy, EULA, and your contract with them (if applicable). Those are the bits that have legal enforceability.