You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Trace: a moved Claude Code transcript stops the session evidence #3669
Chainloop Trace sends no evidence for a Claude Code session after Claude Code moves the transcript of that session. The commits keep the Chainloop-Trace-Sessions trailer, but each push logs this warning and attests nothing:
WRN could not read the transcript of an AI session named in the pushed commits; no evidence is sent for it
INF no new AI coding session evidence to attest
The session record keeps the transcript_path of the first hook that reported one. A later hook that reports another path does not change it. Pre-push copies the transcript from the recorded path, so when that file is gone, the session has no evidence for the rest of its life.
How it happens
Claude Code files a transcript under the project folder of the directory where the session runs (~/.claude/projects/<encoded directory>/<session id>.jsonl). In one observed case:
A session started in a repository and then worked in a git worktree of it. Claude Code wrote the transcript under the project folder of the worktree, and Trace recorded that path.
The user quit Claude Code and resumed the session. The transcript is now under the project folder of the repository, and the file under the worktree folder is gone.
The session-start hook of the resumed session and each later hook reported the new path. Trace kept the old path, and each later push attested nothing.
Expected
When a hook reports a transcript path and the file of the recorded path is gone, Trace records the new path, so pre-push finds the transcript.
Activity