Problem

Currently, all settings in claudecodeui are stored in localStorage, which means:

• Settings are lost when clearing browser data
• Settings cannot be shared across devices or team members
• No integration with Claude CLI's existing settings files
• Different settings for different projects require manual switching

Proposed Solution

Add support for hierarchical settings files that:

1. Read from ~/.claude/settings.json (global settings)
2. Allow project-specific overrides via {project}/.claude/settings.json
3. Automatically convert Claude CLI format to claudecodeui format
4. Maintain backwards compatibility with existing localStorage settings

Benefits

• Persistent Configuration: Settings survive browser data clearing
• Claude CLI Compatibility: Users can reuse their existing Claude CLI settings
• Team Collaboration: Settings can be committed to version control
• Project Flexibility: Different settings per project without manual switching

Implementation Plan

• Create settings loading/saving functions
• Implement Claude CLI format conversion
• Add API endpoints for settings management
• Update UI to show current settings source
• Add visual indicators for allowed/disallowed tools

Related

I've implemented this feature in PR #108