claude-code - 💡(How to fix) Fix Regression: `/effort` now persists globally; previously was per-session [2 comments, 2 participants]

TL;DR

To fix the issue, consider adding an effortLevelPerSessionOptIn flag to allow users to opt-in for per-session effort level behavior.

Guidance

• Review the current implementation of the /effort command to understand how it writes to settings.json and persists across sessions.
• Investigate the fastModePerSessionOptIn flag to see how it achieves per-session behavior and apply similar logic to effortLevel.
• Consider adding a new flag, effortLevelPerSessionOptIn, to provide users with the option to choose between per-session and persistent effort level behavior.
• Test the proposed solution with multiple sessions to ensure the effort level is reset correctly when the flag is enabled.

Example

No code snippet is provided as the issue does not contain sufficient implementation details.

Notes

The proposed solution assumes that the fastModePerSessionOptIn flag is implemented correctly and can be used as a reference for the effortLevelPerSessionOptIn flag. Additional testing and verification are necessary to ensure the fix works as expected.

Recommendation

Apply workaround: Add an effortLevelPerSessionOptIn flag to allow users to opt-in for per-session effort level behavior, providing more control over the effort level persistence.