ashlr

Permissions

How /ashlr-allow works and what it writes to your settings.

Claude Code prompts for permission the first time MCP tools are called. /ashlr-allow writes ashlr allowlist wildcards so those prompts do not interrupt first use.

What it does

Running /ashlr-allow invokes scripts/install-permissions.ts, which:

  1. Reads ~/.claude/settings.json (or creates it).
  2. Appends ashlr MCP wildcard entries to permissions.allow.
  3. Writes the file back.

Entries added

{
  "permissions": {
    "allow": [
      "mcp__ashlr-*",
      "mcp__plugin_ashlr_*"
    ]
  }
}

Scope

/ashlr-allow writes to the user-level ~/.claude/settings.json by default. To target a different settings file, pass --settings:

bun run ~/.claude/plugins/cache/ashlr-marketplace/ashlr/scripts/install-permissions.ts --settings /path/to/settings.json

Dry run

Preview what would be written without writing:

bun run ~/.claude/plugins/cache/ashlr-marketplace/ashlr/scripts/install-permissions.ts --dry-run

Undo

bun run ~/.claude/plugins/cache/ashlr-marketplace/ashlr/scripts/install-permissions.ts --remove

This removes only the ashlr entries and leaves the rest of settings.json intact.

Reload required

After any settings change, run /reload-plugins before the new permissions take effect. If reload is unavailable, fully quit and restart Claude Code.

On this page