{"version":"2.1.309","anchor":"claude-ultrareview-gains-a-trust-workspace-flag","canonical_anchor":"claude-ultrareview-gains-a-trust-workspace-flag","heading":"claude ultrareview can trust the current folder for one run","tier":"use","area":"Ultrareview","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/claude-ultrareview-gains-a-trust-workspace-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### `claude ultrareview` can trust the current folder for one run\n\n`claude ultrareview --trust-workspace` trusts the current folder for that run only, without a prompt, so reviews can run in scripts and CI\n\n**What**\n\n`claude ultrareview` now accepts `--trust-workspace`. Normally Claude Code may ask whether you trust a folder before it works in it. With this option it trusts the current folder for that one run without asking, which is meant for scripts and CI (automated build systems where nobody is there to answer a prompt).\n\n- The option takes no value. If you put a value after it, the run stops with \"Ultrareview did not start\" and an error saying the option takes no value.\n\n- Without the option, the command may still ask about trust. Whether it does also depends on `CLAUDE_CODE_DISABLE_ULTRAREVIEW_TRUST_CHECK` and on a setting Claude Code receives from Anthropic's servers.\n\nThe self-hosted runner already had its own `--trust-workspace [bool]` option. This is the same name added to the `ultrareview` command.\n\n**Why**\n\nReviews can now run unattended in CI. Trusting a folder also means Claude Code honours that folder's git configuration and project settings, so use the option only on code you are willing to trust.\n\n- Area: Ultrareview\n- Names: `--trust-workspace`, `claude ultrareview`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}