Modes
New conversations start in sets the default mode for new conversations. It is marked All machines because it applies whichever host a conversation runs on. The default is Full access. A card for each mode lists what that mode runs without asking.
Auto is experimental. We’re still improving its reliability and speed. It appears last in the permission picker, and it carries an Experimental label in the picker, on its mode card, and on the Judge tab.
In Auto mode, edits to files that define what runs later still ask you, because the judge can’t see what such an edit changes. These include git internals and hooks, CI workflows, project manifests and build or test configuration (such as
package.json, Makefile or pyproject.toml), editor and agent settings (such as .vscode/tasks.json or .claude/settings.json), SSH configuration, and the repository’s .traycer/auto-policy.md and .traycer/environment.json.
You can change the mode for any conversation from the composer. A new composer starts from the settings you last ran with on that host (for a new conversation in a Task, the ones you last used in that Task), mode included. New conversations start in applies when there are none.
This default applies only to conversations you start in the app. Agents created from the CLI or by another agent start in Full access unless their creator passes --permission-mode.
Judge
The judge is the model that reviews commands when a conversation runs in Auto mode. This choice is stored on the host you are editing.When GitHub Copilot does the reviewing, either because you chose it or because Automatic falls back to a Copilot conversation’s own provider, the judge uses Copilot premium requests: about 60–350 per hour of Auto mode, billed on top of the conversation.
Providers With A Built-In Reviewer
Some providers can review their own commands. Claude Code can use its own classifier instead of Traycer’s judge. It is faster and costs nothing extra, but your rules do not apply to it. For that provider’s conversations, the built-in reviewer takes the place of the judge above. Choose Traycer’s judge or the provider’s classifier for each provider here, or on that provider’s Permissions tab in Providers. If the provider’s own auto mode is unavailable, for example because an administrator turned it off, Traycer’s judge reviews that turn and the chat says so.Rules
Rules tell the judge what to trust and what to bring to you. Your rules add to Traycer’s built-in ones, which you can expand under Built-in to read. They are saved to your account and apply on every machine.
Click Save rules to apply your changes, or Discard to drop them.
Allow From Now On
When the judge sends you an action only because you didn’t ask for that exact action, the approval card says “Sent to you because you didn’t ask for this exact action.” and offers Allow from now on…. The same link appears on those decisions in Activity. Allow from now on… opens the Rules tab with a drafted Always allow rule that names the judge’s rule and the exact action. When Traycer knows where the conversation runs, the draft is narrowed to that repository and worktree branch. Edit the draft if you want it broader or narrower, then click Save rules. Nothing changes until you save.Repository Rules
A repository can add its own rules in a committed file:Activity
Recent decisions lists what the judge decided on this host: when, in which conversation, which action, the outcome, and why. The host keeps the last 200 decisions. Filter by All, Allowed, Asked you, Refused, or Couldn’t decide. Commands the judge approves run without a card in the conversation, so this is where to check them. Decisions stay on the host and are not synced. For a conversation reviewed by a provider’s built-in classifier, Activity shows what the classifier allowed. What it refused reaches you as an ordinary approval and isn’t listed here.If a host predates Auto mode, the Auto option says Needs a newer
Traycer on this machine, and these tabs ask you to update the host. See
Overview.