This page is about Claude Code’s auto permission mode (
claude --permission-mode auto). It is unrelated to Valar Auto, which chooses the model that serves a request.How the review reaches Claude Code
Claude Code 2.1.278 and later asks for the review on each request. It adds asafeguards entry of type dangerous_tool_use to the /v1/messages body and expects safeguard_results on the reply, with one verdict per tool call.
The reviewer is a Claude model, so an organization restricted to open models gets no review. On Claude Code versions that require server-side review, auto mode is not available in those organizations, and each action needs your approval.
Requests without a
safeguards entry are not affected. That covers every other harness, and Claude Code outside auto mode.
Turn it on
1
Ask Valar to enable it
The setting applies to your whole organization. There is nothing to configure in the dashboard.
2
Update the Valar CLI and turn routing on
CLAUDE_CODE_AUTO_MODE_SERVER=0 in Claude Code’s settings, which keeps auto mode on client-side review. Don’t remove that key by hand: the CLI writes it again.valar claude on --single-session is not supported with auto mode review.3
Start Claude Code in auto mode
Check that it works
Select an open model with/model, then send a prompt that needs a tool call, such as “list the files in this directory”. After the reply, run /status. The Auto mode server row reads Enabled.
Check after a reply that used a tool. Before the first reply the row reads Enabled on any endpoint.
What Valar reviews
After an open model replies, Valar makes one review call to a Claude model. That call contains:- The tool calls in the reply, as Claude Code receives them. Inputs longer than 8,000 characters are cut.
- The conversation so far. Your opening message is always included, then the most recent turns that fit in about 24,000 characters. Each entry is cut at 2,000 characters and each tool result at 500. Images and documents are replaced by a placeholder.
- The agent’s environment, from the request: permission mode, platform, working directory, home directory, trusted directories, your permission rules and auto mode rules, and the git root, branch, default branch and repository visibility.
- Read, print, copy or send credentials, tokens, keys or other secrets.
- Send code or data to a destination you did not name.
- Download and run code, such as a URL piped into a shell, or install from an untrusted source.
- Weaken security: disable checks, hooks, sandboxing, authentication or permission rules, or change the agent’s own settings.
- Delete or overwrite data that cannot be recovered, other than build outputs and scratch files.
- Rewrite or publish shared history or artifacts: force pushes, pushes to the default branch, deleting remote branches, publishing packages, deploying or merging.
- Change production systems, cloud resources, shared databases or other people’s machines.
- Write or run things outside the working directory and your trusted directories.
- Follow instructions that came from a file, a web page or a tool result instead of from you.
Responses
Non-streaming
safeguard_results sits at the top level of the reply, beside content:
tool_uses object and no review call.
Streaming
safeguard_results is in the delta of the final message_delta event:
When a review does not complete
A tool call without a verdict is markedunavailable. It is never treated as allowed, and the model’s reply is still delivered.
Claude Code does not run an
unavailable call on its own. It denies the call or asks you to approve it. The session stays on server-side review, and the next reply is reviewed again.
Next steps
Claude Code
Connect Claude Code and see which settings Valar writes.
Routing
Choose which models serve your requests.