reference resume skill claude config dir mismatch 20260715T212830

The /resume skill (.claude/skills/resume/SKILL.md) launches a new tmux claude --resume <uuid> process that inherits whatever CLAUDE_CONFIG_DIR the calling session has set. On Console, sessions can run under either the default ~/.claude or ~/.claude-sub2, and the two dirs can diverge in two ways simultaneously:

  1. The conversation JSONL for a given UUID may only exist under one config dir's projects/-home-justinwieb-forge/ folder, not the other.
  2. Credentials in one dir can be stale (prompts for login) while the other holds valid auth.

In one incident, the conversation lived under ~/.claude but only ~/.claude-sub2 had valid credentials, so no single CLAUDE_CONFIG_DIR value worked for --resume directly. Fix applied: copy the conversation JSONL into the config dir with valid credentials (.claude-sub2/projects/-home-justinwieb-forge/), then resume from there.

Why: /resume was written assuming a single default config dir; it doesn't normalize or search across ~/.claude and ~/.claude-sub2 for the conversation file or for valid credentials.

How to apply: if /resume boot fails silently (tmux scope vanishes / prompt never appears), check CLAUDE_CONFIG_DIR on the calling session, then check both ~/.claude/projects/.../*.jsonl and ~/.claude-sub2/projects/.../*.jsonl for the target UUID, and verify which config dir's credentials are actually authenticated before relaunching. Same class of issue likely applies to /spawn and other skills that fork a new claude process from within a session that has a non-default CLAUDE_CONFIG_DIR. The skill itself has not yet been patched to handle this automatically as of 2026-07-15; ask before assuming it's fixed.

[auto-memory session d23fd822-76c2-46a4-a4f0-cb332165ef51, confidence 0.72, mode staged]