Claude Code sessions from custom CLAUDE_CONFIG_DIR are not detected

[voyvodka]

Problem

Claude Code supports custom config directories via the CLAUDE_CONFIG_DIR environment variable. This is commonly used to maintain separate profiles:

# default
claude                                       # uses ~/.claude/

# custom profiles
CLAUDE_CONFIG_DIR=~/.claude-personal claude  # uses ~/.claude-personal/
CLAUDE_CONFIG_DIR=~/.claude-work claude      # uses ~/.claude-work/
CLAUDE_CONFIG_DIR=/opt/my-config claude      # any arbitrary

Each profile stores its sessions independently under its own projects/ directory. Currently editors/claude.js only scans ~/.claude/projects/, so all sessions from custom profiles are completely missed.

The config directory can be any arbitrary path — not necessarily under ~/ or following a .claude-* naming convention — so a glob-based auto-detection alone wouldn't cover all cases.

In my case, only 135 out of 606 sessions (22%) are being detected — the remaining 471 sessions across two additional profiles are invisible to Agentlytics.

Expected behavior

Sessions from all Claude Code config directories should be discovered and included in analytics.

[f]

Do you have any proper solution for this?

[voyvodka]

I've been working on a solution for this. My approach uses fingerprint-based discovery:

1. Scan hidden directories under ~/ and check if both projects/ dir and history.jsonl file exist — this combination is a reliable Claude Code config directory signature
2. Also read CLAUDE_CONFIG_DIR env var if set
3. Merge sessions from all discovered directories, deduplicating by session ID

This covers the common patterns (~/.claude-personal, ~/.claude-work, etc.) automatically without requiring user configuration.

Known gap: Arbitrary non-home paths (e.g. /opt/my-config) that aren't set in CLAUDE_CONFIG_DIR at runtime won't be discovered. A user-defined directory list in agentlytics config could complement this for edge cases.