Preserve user env settings during provider switch#79
Conversation
Only remove settings.json env entries that conflict with the active provider env so user-managed Claude and Anthropic environment variables remain intact. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Closing: superseded by #76 (already merged on main), which fixes the same issue (user env in settings.json being wiped) with a safer approach. Empirical finding (claude 2.1.144): settings.json Consequence: this PR's narrower cleanup (keeping user ANTHROPIC_/CLAUDE_ in settings.json + removing |
Repository was renamed back to claude-code-config-switcher after supervisor mode removal in 0.4.0. - README/README-CN: update release download/listing URLs - CHANGELOG: update compare links; note repo rename in 0.4.0 entry - docs/discuss-20260519-env-priority.md: update PR guyskk#79 link - docs/supervisor-mode-improvement-proposal.md: update project link Historical entries (0.2.0 rename note, frozen plan snapshots) left intact as historical records.
Summary
ANTHROPIC_*andCLAUDE_*env settings unless the active provider defines the same keyTest plan
go test ./internal/config ./internal/provider./check.sh🤖 Generated with Claude Code