Free toolRuns in your browser

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.

Settings files

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.

Permission mode
The link keeps everything after the # sign, which your browser never sends to a server.

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 find and read-only forms of git as 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, sed and tee name. 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 .git and .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.

Install script
curl -fsSL https://euthyne.com/install | sh
Homebrew
brew install euthyne-labs/tap/euthyne

euthyne init signs you in first, or lets you create an account. Request access or read the docs.

Frequently asked questions

Related

Where to go next

Euthyne
EuthyneBordeaux