Compat: honor permissions from .claude/settings.json

[aakashrajput]

---

Why

Teams switching from Claude Code have curated permissions.allow/deny/ask lists in .claude/settings.json. Honoring them makes switching frictionless and keeps their guardrails intact.

What

• Read .claude/settings.json (and .claude/settings.local.json, local wins) from the project root
• Map permissions.allow / deny / ask rules onto our permission layer. Rule shapes to support: Bash(git *), Edit(src/**), Read(...), WebFetch(domain:example.com), bare tool names. Map tool names to ours (Bash→run_command, Edit→edit_file/multi_edit/apply_patch, etc.); log unmappable rules and skip
• Precedence: deny > ask > allow; our native config always outranks imported rules
• Gate behind config flag (default on), log a summary line at startup

Where to start

• src/permissions/index.ts — current 3-tier model; this adds a rule-matching layer in front
• Keep the matcher a pure function with table-driven tests

Acceptance criteria

• Fixture tests: allow/deny/ask each honored, glob patterns, precedence, unmappable-rule skip
• No behavior change when no .claude/settings.json exists
• typecheck + tests green

[siddhanttiwari19]

Hi @aakashrajput, I'd like to work on this. Plan: add a rule-matching layer in front of the existing 3-tier model insrc/permissions/index.ts load`` .claude/settings.json+ .claude/settings.local.json (local wins), map allow/deny/ask rules for the four shapes listed (bare tool names, Tool(pattern), WebFetch(domain:...)), skip+log unmappable rules, deny > ask > allow with our native config always taking priority, gated behind a config flag (default on). Matcher as a pure function with table-driven fixture tests covering each shape, precedence, globs, and the no-.claude/-present no-op case.

Could you assign this to me?

[aakashrajput]

@siddhanttiwari19, just add a PR linking the Issue, thanks. Also, you can join our Discord to see contribution updates, etc., and if you have some suggestions to discuss over there.

[siddhanttiwari19]

Hi.. @aakashrajput I'd like to join the project's Discord to stay updated on contributions, but I couldn't find the invite link in the repository. Could you please share the Discord invite?

[aakashrajput]

Hi @siddhanttiwari19 you can find the link in klaatcode readme.

[siddhanttiwari19]

Hi @aakashrajput , this PR addresses #37 by adding the Claude settings compatibility layer with the requested precedence rules, local overrides, and test coverage.
Could you please review it when you have a chance.