[BUG] `claude config get --global env` not showing env in settings.json
Resolved 💬 3 comments Opened Jun 7, 2025 by rockmandash Closed Jun 7, 2025
Environment
- Platform (select one):
- [ ] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [x] Other: Claude CLI
- Claude CLI version: 1.0.17 (Claude Code)
- Operating System: macOS
- Terminal: VSCode integrated terminal
Bug Description
Configuration settings manually added to ~/.claude/settings.json are not recognized by claude config get commands, causing inconsistency between the actual config file content and what the CLI reports.
Steps to Reproduce
- Manually edit
~/.claude/settings.jsonto add environment variables:
``json``
{
"env": {
"DISABLE_ERROR_REPORTING": "1",
"DISABLE_TELEMETRY": "1"
}
}
- Save the file
- Run
claude config get --global env - Observe that the command returns
{}instead of the configured values
Expected Behavior
The claude config get --global env command should return the environment variables that are present in the ~/.claude/settings.json file:
{
"DISABLE_ERROR_REPORTING": "1",
"DISABLE_TELEMETRY": "1"
}
Actual Behavior
The claude config get --global env command returns an empty object {}, even though the settings are present in the configuration file.
Additional Context
- The
cat ~/.claude/settings.jsoncommand shows the configuration is properly saved
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗