Skip to content

learn-taste: support non-standard Claude Code config paths (e.g. CLAUDE_CONFIG_DIR) #438

@jasonpaulso

Description

@jasonpaulso

Context: Some projects use a shared Claude Code config directory at a non-standard path (e.g. ~/Developer/Work/Busie/.claude/) instead of the default ~/.claude/.

Problem: The learn-taste command hardcodes session discovery to ~/.claude/projects/. For Busie's fe-main project, this meant only 11 sessions were found in the standard location, while 33 sessions existed at ~/Developer/Work/Busie/.claude/projects/-Users-jasonschulz-Developer-Work-Busie-fe-main/.

Workaround applied: Symlinked the non-standard sessions into the standard location:

ln -sf ~/Developer/Work/Busie/.claude/projects/-Users-jasonschulz-Developer-Work-Busie-fe-main/* ~/.claude/projects/-Users-jasonschulz-Developer-Work-Busie-fe-main/

Suggested fix: Add support for discovering sessions from non-standard Claude Code config directories. Options:

  • Detect CLAUDE_CONFIG_DIR environment variable if set
  • Add a --claude-config-dir flag to learn-taste
  • Scan for .claude/projects/ relative to the project root (e.g. ../../.claude/projects/ for monorepo sub-projects)

This would make taste learning work out-of-the-box for teams using shared or project-scoped Claude Code configurations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions