[Feature Request] Configuration Option to Disable Automatic .env Loading
Bug Description
This is about the VS Code extension. When I load VS Code with a project that has .env.development and .env.test files in it, the Claude Code VS Code Extension loads the vars from .env.development. The problem is that when claude then runs commands like bun test, those env vars are defined, therefore the override the values from .env.test. I can confirm this by temporarily renaming those .env files to something else, then I start VS Code and start the Claude Code extension, then the env vars are not set and bun test works. I would like there to be a configuration setting for the extension to allow me to configure it to not load environment variables from files, so I don't have to do this workaround everytime I start VS Code.
Environment Info
- Platform: darwin
- Terminal: vscode
- Version: 2.0.14
- Feedback ID: 1e037647-7d41-442c-a695-13fc83f4a9c2
Errors
[]This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗