claude-code - 💡(How to fix) Fix Allow configurable .claude/ directory location (support parent directory) [1 comments, 2 participants]

TL;DR

The issue can be addressed by introducing a configuration option to specify the location of the .claude/ directory, allowing it to reside in a parent directory with project-specific subfolders.

Guidance

• Introduce a new setting, such as "projectStateDir" in ~/.claude/settings.json, to control the location of the .claude/ directory.
• Update the CLI to respect this setting and create the .claude/ directory in the specified location, rather than the current working directory.
• Consider adding a command-line flag to override the setting, allowing users to specify the directory location on a per-command basis.
• Verify the fix by running Claude Code from a project subdirectory and checking that the .claude/ directory is created in the expected location.

Example

// ~/.claude/settings.json
{
  "projectStateDir": "parent"
}

This example shows how the projectStateDir setting could be configured in the ~/.claude/settings.json file.

Notes

The proposed solution assumes that the .claude/ directory can be safely moved to a parent directory without disrupting existing functionality. Additional testing may be necessary to ensure that this change does not introduce any regressions.

Recommendation

Apply workaround: Introduce the projectStateDir setting and update the CLI to respect it, as this allows users to control the location of the .claude/ directory and avoid polluting the project directory with tool infrastructure files.