{"version":"2.1.310","anchor":"serialization-guard-also-rejects-vm-contexts","canonical_anchor":"serialization-guard-also-rejects-vm-contexts","heading":"Error for values that cannot be copied now also names vm contexts","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/serialization-guard-also-rejects-vm-contexts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Error for values that cannot be copied now also names vm contexts\n\nThe error shown when a value cannot be copied now says it holds a Proxy or a vm context, and the check runs in one more place\n\n**What**\n\nSome values cannot be copied safely from one part of a program to another. Claude Code already refused values containing a Proxy (a JavaScript object that intercepts access to another object). The error message now reads \"holds a Proxy or a vm context\", so values holding a vm context (an isolated JavaScript environment) are caught too. The same shared check is now also used in a second place.\n\n**Why**\n\nThis is a small robustness change: a wider set of values that cannot be copied is caught with a clear message instead of failing in a less obvious way.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}