microsoft / microsoft/AI-Engineering-Coach
Feature request: Allow configurable Claude config directories
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 588
- Avg merge
- 22h 5m
- Merged PRs (30d)
- 16
Description
Summary
Allow users to explicitly specify Claude configuration root directories via a setting (e.g. aiEngineerCoach.claudeConfigDirs), rather than relying solely on automatic discovery (CLAUDE_CONFIG_DIR env var or ~/.claude).
Motivation
Some users have Claude configurations in non-standard locations. Providing an explicit setting would:
- Support custom Claude config paths
- Allow multiple config roots
- Enable Claude-only parsing when no VS Code/Xcode log directories exist
Proposed behavior
- Add a setting like
aiEngineerCoach.claudeConfigDirsfor explicit Claude config root selection - Keep automatic discovery via
CLAUDE_CONFIG_DIRand~/.claudeas fallback when the setting is unset - Deduplicate config roots via realpath and sessions by sessionId
References
Originally proposed in #65 by @cainrus.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the VS Code setting registration and the existing Claude configuration discovery logic, including CLAUDE_CONFIG_DIR and ~/.claude handling. Add explicit config-root selection while preserving fallback discovery, then verify realpath root and sessionId deduplication and Claude-only parsing when no VS Code/Xcode log directories exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100