pstack Files

claude-project-dir.mjs now finds this session's transcripts directory from CLAUDE_CODE_SESSION_ID, which Claude Code sets in its shell. It returns the directory under projects/ that holds <id>.jsonl or <id>/<id>.jsonl, and reads only names. A bare <id>/ does not count, because Claude Code's Workflow tool creates one under the shell's current project. In 0.9.100 the skills passed the system prompt's primary working directory, and that label follows the shell rather than the directory the session started in. After the agent moved into a worktree, recall, automate-me, reflect, show-me-your-work, and the Eval and Session pickup playbooks got exit 1. After a move into another project with transcripts of its own, they read that project's chats. The skills now run the script without an argument. A test fails if any of them passes the primary working directory again. Session pickup passes an earlier session's start directory when that session started somewhere else.

With an argument, the script derives the name from that directory and skips the session lookup. Without a session id, as in a Claude Code release that does not set one, it derives the name from the current directory, as before. It no longer trims CLAUDE_CONFIG_DIR, because Claude Code uses the value as given.

Verified. The new test, a session whose transcript sits under a directory other than the one the workspace path derives, fails on 0.9.100 and passes here. This session ran from another directory: the script printed this session's directory, and the reflect line found its transcript.