Docs say vault_ids cannot change mid-session, and deployments now have an update endpoint.
What's wrong with this entry?
Session 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.
- A deployment can carry a
budgetthat is copied onto every session it fires; it can be cleared and added back at the deployment level.
` vault_ids is create-only (rejected on update) `
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Question options with identical text are no longer confused with each other
Both mention agent
-
v2.1.236
Teammate messages whose summary swallowed the body are split back apart
Both mention agent
-
v2.1.238
Claude is told to stay in a worktree even when it did not create one
Both mention agent