Detection edge case: sessionId mismatch + same-cwd + no cross-ref

[grimmerk]

Problem

Detection can still assign the wrong purple dot when all of these conditions are true simultaneously:

1. sessions/ sessionId doesn't match history.jsonl (confirmed: after /clear; also observed once for unknown cause)
2. Multiple same-cwd sessions exist
3. Cross-reference fails:
   • Ghostty: no per-tab TTY (pending upstream #11592)
   • iTerm2/cmux: sessions have no /rename (tab names identical, can't disambiguate)

In this case, cwd fallback picks the first unclaimed same-cwd session — which may be wrong.

Practical likelihood

Very low. Requires a rare trigger (/clear or unknown) + same-cwd + no /rename + Ghostty (or no /rename on iTerm2/cmux).

Related

• Use ~/.claude/sessions/ for reliable active session detection + VS Code support #65 — sessions/ detection rewrite
• feat: rewrite detection with sessions/ PID files + cross-ref fallback #67 — PR implementing sessions/ detection + cross-ref fallback
• Ghostty: no per-tab TTY/PID — missing cross-reference and TTY switch fallback #63 — Ghostty/cmux TTY support tracking

🤖 On behalf of @grimmerk — generated with Claude Code