Claude Code permission simulator
Paste your Claude Code settings, list the tool calls you care about, and see whether Claude Code allows each one, asks first or denies it, which rule decides and which file that rule comes from. It runs Euthyne’s permission evaluator in your browser. Nothing you paste is uploaded.
Applies to every project on your machine.
One per line: Bash(git push --force), Edit(src/app.ts), Read(~/.ssh/id_ed25519), WebFetch(domain:example.com), mcp__github__create_issue, a plain shell command, or a PreToolUse hook payload in JSON.
The verdicts appear here once the evaluator loads, about 1.6 MB the first time. It runs in this tab: nothing you paste leaves your browser.
- Allowedruns without a prompt
- Asks firstClaude Code prompts you
- Deniedthe call is blocked
- Can't tella deny rule may cover it, so expect a deny or a prompt
How it works
The simulator layers your settings files the way Claude Code does: managed settings, then .claude/settings.local.json, .claude/settings.json and ~/.claude/settings.json. Rules from every file count. For each action, deny rules are checked first, then ask, then allow, and the first match decides, so a deny in any file beats an allow in any other (Claude Code docs).
When no rule matches, the permission mode decides. Reads and built-in read-only commands inside the project run without a prompt, acceptEdits accepts edits inside the project, auto and bypassPermissions skip the prompt, dontAsk denies, and plan mode blocks edits until you approve the plan (permission modes).
The evaluator is the Go code the Euthyne CLI runs on every tool call to record whether the agent stayed inside the permissions in force, compiled to WebAssembly. We test it against the examples in Claude Code’s permission rule documentation. Where it can be wrong:
- Claude Code also treats
findand read-only forms ofgitas read-only commands. The simulator asks for them, and says so. - Claude Code applies Read and Edit deny rules to the files that
cat,head,tail,sedandteename. The simulator doesn’t, and flags the allowed commands where that matters. - Claude Code lets an allow rule match past a few known-safe environment variables, like
NODE_ENV=test npm test. The simulator asks. - It doesn’t model the sandbox, protected paths such as
.gitand.claude, the auto mode classifier, WebFetch’s preapproved documentation domains, or command-line flags such as--allowedTools.
Why it matters
A permission rule is a promise about what an agent may do without you, and broad rules promise more than they look. Bash(git:*) reads like “let it use git”, but it also lets the agent force-push over main, or point core.fsmonitor at a script that git then runs (Claude Code docs).
Deny rules cover less than they look. Bash(curl *) stops curl https://…, not /usr/bin/curl or sh -c 'curl …'. The docs put it plainly: a Bash rule isn’t a security boundary around the program. Pair deny rules with the sandbox, or check commands in a PreToolUse hook.
Settings also drift, per repository and per person. A verdict here is for the files you paste, today. What the agent did last Tuesday is a different question.
See what the agent actually did
The simulator shows what your settings allow. Euthyne records what happened: every Claude Code tool call becomes a signed receipt, checked against the permissions in force when it ran, in an append-only log anchored on-chain. Prompts and outputs stay on your machine, only salted hashes leave.
curl -fsSL https://euthyne.com/install | shbrew install euthyne-labs/tap/euthyneeuthyne init signs you in first, or lets you create an account. Request access or read the docs.
Frequently asked questions
No. The evaluator is WebAssembly that runs in this tab, so what you paste never leaves your browser. A shared link keeps your settings after the # sign, which browsers don't send to servers, and our analytics drop that part of the address too.
User settings (~/.claude/settings.json), project settings (.claude/settings.json), local settings (.claude/settings.local.json) and managed settings, in Claude Code's order. Like Claude Code, it ignores a defaultMode of auto or bypassPermissions in project and local settings.
Every git command, because :* means the same as a space and a *. That includes git push --force, git reset --hard and git -c core.fsmonitor=..., which makes git run a program you name. Put the * after the subcommand, like Bash(git log *), to allow one family of commands.
No. Deny rules still block in bypassPermissions mode, so the simulator shows them as Denied in every column. What bypassPermissions skips is the prompt, so anything no deny rule covers runs. Setting disableBypassPermissionsMode to "disable" turns the mode off.
A deny rule might match part of the command, such as a command inside $(...) or a subshell, or a ! exception in a deny list, and the evaluator doesn't settle those statically. Claude Code checks nested commands against deny and ask rules, so expect a deny or a prompt.
It runs Euthyne's evaluator, which we test against more than a hundred examples from Claude Code's permissions documentation. Where the two differ, for example read-only git commands or the sandbox, the result says so. Claude Code changes often, so check /permissions in Claude Code for the final word.