Description

When I update Claude Code configuration files, the application not only resets/restarts but also clears my authentication, requiring me to re-authenticate from scratch. This disrupts my workflow significantly as I need to go through the entire authentication process every time I make a configuration change.

Expected Behavior

• Configuration updates should be applied without losing my authentication state
• I should remain authenticated across configuration changes
• At most, a simple restart should be required, not a full re-authentication

Actual Behavior

• Updating configuration causes Claude Code to exit/reset
• My authentication state is lost
• I must re-authenticate completely as if using Claude Code for the first time

Steps to Reproduce

1. Authenticate and start using Claude Code normally
2. Update configuration (via /settings command or manually editing config files)
3. Claude Code exits and requires full re-authentication

Impact

This issue significantly disrupts my workflow, especially when I need to adjust configurations frequently. Having to re-authenticate repeatedly is time-consuming and frustrating.

Environment

• OS: Linux 6.6.87.1-microsoft-standard-WSL2
• Platform: linux
• Claude Code version: [Please add your version here]

Additional Context

The authentication tokens/session appear to be cleared when configuration changes are detected, which seems unintended. Authentication state should persist independently of configuration settings.