permission-optimizer

Optimize Claude Code permissions by analyzing tool usage patterns from session JSONL data to suggest additions, removals, and flag security risks in settings.json. It audits Bash, Read, Write, and Edit permissions against defined safe, ask, and deny categories.

Bare entry warnings in Claude permission configurations are potential security risks identified when settings.json entries lack specific constraints. The optimizer flags these bare entries during analysis to prevent vulnerabilities and ensure adherence to safety categories.

Yes, you can audit Claude tool usage patterns to remove unused permissions. The optimizer analyzes past session data to identify which Bash, Read, Write, and Edit permissions are no longer needed, suggesting removals to improve security and workflow clarity.

Unlike manually editing settings.json, the permission optimizer automatically analyzes session data to suggest precise additions and removals based on actual tool usage. It categorizes permissions into safe, ask, and deny actions, preventing security vulnerabilities that manual configuration might miss.

Analyzing Claude permissions requires session data in JSONL format. The optimizer processes these session JSONL files to extract tool usage patterns, comparing them against defined permission categories to generate accurate settings.json recommendations.

Review and update your Claude Code settings.json file regularly to grant necessary access for new tools and revoke permissions for those no longer in use. This prevents security vulnerabilities, addresses bare entry warnings, and maintains workflow clarity.