{"version":"2.1.274","anchor":"agent-spawn-config-now-recognizes-an-isolation-key-end-to","canonical_anchor":"agent-spawn-config-now-recognizes-an-isolation-key-end-to","heading":"Agent spawn config now recognizes an 'isolation' key end-to-end","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/agent-spawn-config-now-recognizes-an-isolation-key-end-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Agent spawn config now recognizes an 'isolation' key end-to-end\n\nSpawning an agent can now carry an 'isolation' setting through to its configuration\n\n**What**\n\nThe list of settings recognized when serializing an agent's spawn configuration (for example, for the SDK) now includes `isolation`, alongside existing settings like `background` and `omitClaudeMd`. Separately, the schema validating spawn options for isolation, observer, and observer message was refactored to use shared helper definitions instead of separate inline ones.\n\n**Why**\n\nThis lets an agent's `isolation` setting actually be carried through when its configuration is passed along, rather than being dropped during serialization.\n\n- Area: SDK\n- Names: `isolation`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}