Claude Code Ultrareview Now Requires Workspace Trust
Claude Code 2.1.309 changes claude ultrareview so it only runs in a trusted workspace. On a terminal it asks for trust, and in scripts it refuses unless the caller passes --trust-workspace. Teams running ultrareview in automation need to add the flag or set an environment variable to opt out of the check.
Key Takeaways
claude ultrareviewnow requires workspace trust, asking for confirmation on a terminal and refusing outright where no prompt is possible.- Scripts must pass
--trust-workspace, a flag that takes no value, so existing automation can break until it is updated. - Argument order matters, because a PR number or base branch has to be placed before
--trust-workspace. CLAUDE_CODE_DISABLE_ULTRAREVIEW_TRUST_CHECK=1disables the check globally, a blunter option than the per-run flag.- The check targets a command that uploads repository contents, so it limits what an untrusted folder can send for review.
- Interactive users see a single extra prompt, while CI owners are the group most likely to need a change.
What changed
Claude Code 2.1.309 changes the claude ultrareview command to require workspace trust. Previously the command did not gate on whether the user had marked the folder as trusted. Now, when run on a terminal, it asks the user to confirm trust. When run anywhere that cannot prompt, such as a script or a CI job, it refuses to run.
This is a behavior change for anyone who has automated claude ultrareview. A job that worked before can now fail until it opts in.
How scripts opt in
Scripts pass the new --trust-workspace flag. The flag takes no value, so it is a bare switch. One detail matters for argument order: any PR number or base branch must come before --trust-workspace on the command line, because the flag does not consume a following argument.
Teams that prefer an environment-level setting can set CLAUDE_CODE_DISABLE_ULTRAREVIEW_TRUST_CHECK=1 to turn the check off entirely. That route is less selective than the flag, since it removes the check for every run in that environment rather than for one invocation.
Why it matters
Ultrareview uploads the contents of a repository for review, so running it against a folder the user has not vetted carries more risk than a local-only command. Gating it on workspace trust brings it in line with how other Claude Code features treat untrusted folders. Interactive users will see one extra confirmation. Automation owners should check their pipelines and add --trust-workspace where the folder is known to be safe.