claude-code - 💡(How to fix) Fix /effort slash command persists to global ~/.claude/settings.json instead of being session-scoped [1 comments, 2 participants]

TL;DR

Modify the /effort command to store its setting in a session-specific configuration file instead of the global ~/.claude/settings.json file.

Guidance

• Review the implementation of the /effort command to ensure it uses a session-specific storage mechanism.
• Verify that the option+p effort toggle also uses the same session-specific storage to maintain consistency.
• Consider adding a session identifier to the settings file name or path to differentiate between sessions.
• Check for any existing configuration options or environment variables that could be used to specify a session-specific settings file.

Example

// Session-specific settings file example
// ~/.claude/session-123/settings.json
{
  "effortLevel": "low"
}

Notes

The current implementation of the /effort command and option+p effort toggle seems to be using the global settings file, which is causing the issue. Modifying the command to use a session-specific settings file should resolve the problem.

Recommendation

Apply a workaround by modifying the /effort command to use a session-specific settings file, as this will allow for session-scoped effort levels without affecting the global settings.