[FEATURE REQUEST] Native IDE Integration for Configuration (VS Code & JetBrains) - Stop Creating .claude Folders

Claude Code Configuration :

Environment

• Platform (select one):
• [x] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• Claude CLI version: 1.0.72 (Claude Code)
• Operating System: Windows 11 Professionnel 24H2 (Build 26100.4770)
• Terminal: PowerShell

Bug Description

Claude Code automatically creates a .claude/settings.local.json folder in every project directory, which pollutes projects and completely ignores IDE-native configuration systems like VS Code and JetBrains. This breaks established IDE conventions and creates a poor developer experience.

Steps to Reproduce

1. Navigate to any project directory
2. Run claude command
3. Claude Code automatically creates .claude/settings.local.json
4. Try to configure Claude Code through VS Code settings.json - nothing works
5. Repeat in multiple projects - each gets its own .claude folder

Expected Behavior

Claude Code should integrate with IDE configuration systems like other professional extensions:

• Configuration through VS Code's settings.json file
• Integration with JetBrains IDE settings
• Centralized permission management
• No automatic creation of project-specific folders
• Settings that sync across machines through IDE

Example VS Code integration:

{
  "claude-code.permissions.allow": ["Bash(grep:*)", "Bash(ls:*)"],
  "claude-code.permissions.deny": [],
  "claude-code.useGlobalSettings": true
}

Actual Behavior

• Every project gets a .claude folder whether you want it or not
• No way to configure Claude Code through VS Code settings
• Must manually manage these files or add .claude/ to gitignore in every project
• Configuration is fragmented across multiple locations
• No centralized permission management possible

Additional Context

This is a significant design issue that affects every Claude Code user working in IDEs. Professional IDE extensions follow IDE conventions - they don't create their own folders and ignore the IDE's configuration system.

The current approach forces developers to either accept unwanted files in their projects or manually manage gitignore entries, which shouldn't be necessary for a professional development tool.

A proper solution would provide native IDE integration while maintaining backward compatibility with the current .claude/ approach for non-IDE usage.