Inconsistent effort level naming: /effort max vs effortLevel: xhigh in settings

Bug / UX Confusion

The CLI command /effort max maps to "xhigh" in settings.json, with no indication that these are the same thing.

Steps to reproduce

1. Run /effort max in Claude Code — it says effort is set to "max"
2. Open ~/.claude/settings.json — it shows "effortLevel": "xhigh"
3. There is no "max" value in the settings schema enum (low | medium | high | xhigh)

Expected behavior

Either:

• The settings schema should use "max" to match the CLI command name, OR
• The CLI and UI should display "xhigh" consistently everywhere, OR
• At minimum, the UI should show "xhigh (max)" so users understand they are the same

Actual behavior

Users who set effort via /effort max and then inspect their settings.json see "xhigh" and don't know if something went wrong or if the value is correct.

Why it matters

This causes confusion and erodes trust — users think the setting wasn't applied correctly or that "max" and "xhigh" are different levels.

🤖 Generated with Claude Code