claude-code - 💡(How to fix) Fix [FEATURE] Split Startup and Runtime env in settings.json

TL;DR

Consider adding a custom hook or modifying the existing settings.json loading mechanism to support runtime environment variable overrides.

Guidance

• Review the changes introduced in Claude Code v2.1.114 to understand the new settings.json loading behavior and how it affects environment variable inheritance.
• Explore the possibility of using hooks to set environment variables at runtime, as mentioned in the Alternative Solutions section.
• Investigate the feasibility of adding a new field to settings.json, such as "runtime_env", to define environment variables that should be set after startup.
• Evaluate the security implications of exposing environment variables like CLAUDE_CODE_OAUTH_TOKEN and consider alternative approaches to hiding sensitive information.

Example

No code example is provided due to the lack of specific technical details.

Notes

The proposed solution requires further discussion and consideration of the potential impact on the Claude Code architecture and security. The Alternative Solutions section mentions using hooks and LLM requests, but their reliability is uncertain.

Recommendation

Apply workaround: Utilize hooks to set environment variables at runtime, as this approach is already mentioned in the issue and may provide a temporary solution until a more permanent fix is implemented.