{"version":"2.1.265","anchor":"workspace-trust-plumbed-into-init-config-and-sdk-session-req","canonical_anchor":"workspace-trust-plumbed-into-init-config-and-sdk-session-req","heading":"Workspace trust plumbed into init config and SDK session request","tier":"internal","area":"Workspace Trust","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/workspace-trust-plumbed-into-init-config-and-sdk-session-req","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Workspace trust plumbed into init config and SDK session request\n\nWorkspace trust status is now passed into session setup and checked against trusted network directories\n\n**Unclear.** What happens as a result of this workspace-trust check (e.g. what gets blocked or warned) is not stated.\n\n**What**\n\nA `workspaceTrust` setting from init configuration is now passed through to session setup, where it's used to run a new workspace-trust check. That check considers the current working directory, a list of trusted network directories, and storage state, and runs during setup when the host owns the terminal's standard input.\n\n**Why**\n\nThis threads workspace trust information deeper into session initialization, likely as part of deciding what a session is allowed to do in an untrusted workspace, though the finding doesn't specify the effect of the check's result.\n\n- Area: Workspace Trust\n- Names: `workspaceTrust`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}