{"version":"2.1.317","anchor":"trust-workspace-help-text-and-no-project-trust-seeding","canonical_anchor":"trust-workspace-help-text-and-no-project-trust-seeding","heading":"Self-hosted runners can start sessions without trusting the workspace","tier":"use","area":"Self-Hosted Runners","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/trust-workspace-help-text-and-no-project-trust-seeding","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Self-hosted runners can start sessions without trusting the workspace\n\nSelf-hosted runners now skip trusting the workspace when a new server-config check passes, and the --trust-workspace help describes a stricter gate\n\n**Unclear.** It is not clear what condition makes a self-hosted runner skip saving trust.\n\n**What**\n\nTrusting a workspace means Claude Code accepts the settings stored in the project folder. A self-hosted runner is a machine you run yourself that starts Claude Code sessions.\n\n- The runner now skips seeding trust when a new check on the server config is satisfied, and logs \"Seeded no persisted trust\". Before, trust was always seeded when trusting was enabled.\n\n- The child session's `trustWorkspace` is now only set when trusting is enabled and that check is not satisfied. Before, it followed the trust setting alone.\n\n- The help text for `--trust-workspace` now describes a stricter gate when it is set to false.\n\n**Why**\n\nIn those cases the session starts without the project setting source, so settings stored in the repository may not be applied on self-hosted runners.\n\n- Area: Self-Hosted Runners\n- Names: `--trust-workspace`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}