Feature request: a supported way to resolve a project's transcript/config directory (external tools re-implement the path-slug encoding and break on every change)
Environment: Claude Code 2.1.237, Linux/Windows/macOS.
Context: Agent Console (and, judging by the tracker, several other integrations) needs to locate a project's transcript directory under ~/.claude/projects/ to offer resume, usage stats and memory features. Today the only way is to re-implement the path→slug encoding by hand.
What broke: 2.1.224 changed the encoding for paths >200 chars (fixing transcripts landing in another project's dir). That fix is correct — but every external tool that mirrors the old encoding now silently resolves the wrong directory for long paths. There's no way to know the new encoding except reverse-engineering, and no guarantee it won't change again. #88418 shows the same class of problem from another side (one project stored under three path spellings).
Ask: any one of these would fully solve it:
claude projects resolve <path>→ prints the transcript dir (ideal), or- a documented, stability-guaranteed spec of the encoding, or
- the resolved dir exposed in hook payloads /
claude auth status --json.
I maintain the integration end of this and can validate a solution quickly.