claude-code - 💡(How to fix) Fix Improve error message when ENV_SCRUB conflicts with --dangerously-skip-permissions [1 participants]

When CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=1 is set in ~/.claude/settings.json and you run claude --dangerously-skip-permissions, the error message is: UX improvement — the underlying behavior (blocking conflicting modes) is correct, just the error message needs to be more user-friendly.

TL;DR

To resolve the issue, update the error message to clearly indicate the conflict between CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=1 and --dangerously-skip-permissions, and provide actionable steps to fix the conflict.

Guidance

• Review the current error message and identify areas for improvement to make it more user-friendly and clear.
• Consider adding explicit instructions on how to resolve the conflict, such as setting CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=0 or removing the --dangerously-skip-permissions flag.
• Ensure that the error message accurately reflects the underlying behavior and the reason for the conflict.
• Test the updated error message with different scenarios to ensure it provides the expected guidance.

Example

An example of an improved error message could be:

⚠ --dangerously-skip-permissions cannot be used while CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=1 is set (they conflict: one grants full access, the other restricts subprocess credentials).

To fix, either:
  • Set CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=0 in ~/.claude/settings.json
  • Or run: CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=0 claude --dangerously-skip-permissions

Notes

The improved error message should be implemented in the Claude Code version 2.1.100 or later, as the conflict check was introduced in this version.

Recommendation

Apply a workaround by updating the error message to provide clear and actionable guidance to users, as the underlying behavior is correct and only the error message needs improvement.