{"version":"2.1.224","anchor":"vault-ids-documented-as-create-only-and-deployments-can-be-u","canonical_anchor":"vault-ids-documented-as-create-only-and-deployments-can-be-u","heading":"vault_ids documented as create-only, and deployments can be updated","tier":"notice","area":"Agent SDK Docs","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/vault-ids-documented-as-create-only-and-deployments-can-be-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### `vault_ids` documented as create-only, and deployments can be updated\n\nDocs say vault_ids cannot change mid-session, and deployments now have an update endpoint.\n\n**What**\n\nSession update docs now state that `vault_ids` is rejected on update even though the SDK exposes it as a parameter, so only `agent.tools`, `agent.mcp_servers`, title, metadata and budget can change mid-session. Deployments gain an `UpdateDeployment` endpoint and `deployments.update` SDK method.\n\n**Details**\n\n- A deployment can carry a `budget` that is copied onto every session it fires; it can be cleared and added back at the deployment level.\n\n**Evidence**\n\n`` `vault_ids` is create-only (rejected on update) ``\n\n- Area: Agent SDK Docs\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}