ZeroTwo remembers permission rules that decide whether a tool call is allowed, needs your approval, or is denied. They cover shell commands, file writes, MCP tools and web domains. They are not written in rule files: in the desktop app you create them from the approval card or by importing them.
Create a rule
Approval cards, the always option and Settings > Import of local agent files are part of the ZeroTwo desktop app. On the web the composer has no permission picker and runs use Full access inside the cloud sandbox, so they do not ask for approval.
-
Wait for an approval
When the agent asks to run a command, edit a file or call a tool, the approval card lists numbered choices.
-
Choose the always option
The last affirmative choice saves a rule so the same kind of call is not asked about again. ZeroTwo applies it for the rest of the run and sends it with later runs.
-
Import existing rules
In the desktop app, Settings > Import brings in permission rules from other agents installed on your computer. ZeroTwo
prefix_ruleentries in arules/folder are converted intoBash(<command> *)rules:allowstays allow andpromptbecomes ask. Entries that cannot be converted, includingforbiddenones, are skipped and flagged for review.
There is currently no screen for browsing, editing or deleting saved rules, so only create an always rule for calls you are comfortable approving permanently.
Rule format
Rules use Tool(content) strings, in three lists: allow, ask and deny. Matching is case-insensitive on the tool name.
| Rule | Matches |
|---|---|
Bash | Every shell command |
Bash(npm run *) | Shell commands that match the wildcard |
Write(src/**) | Writes to paths that match the pattern |
mcp__gmail__send | One specific MCP tool |
When several things apply to a call, the order is: deny rules first, then the read-only restriction of Plan mode, then ask rules, then allow rules, and finally the default for the current permission preset. A deny rule therefore always wins.
Connector tool permissions
Rules for connector tools also have a separate, visible control. In Customize > Connectors, each tool of a connector can be set to Always allow, Needs approval or Blocked.
Scope and limits
In the desktop app, rules sit on top of the permission preset in the composer: Ask for approval, Approve for me or Full access. ZeroTwo itself has no .rules files, no Starlark rule language, and no command for testing a rule file.