4 ms·

I've been attaching to my commit messages a Git Trailer [1] of the Session UUID from the Claude Code conversation that created that commit. It allows Claude to

I've been attaching to my commit messages a Git Trailer [1] of the Session UUID from the Claude Code conversation that created that commit. It allows Claude to look back into the session where a change was made and see the decisions made, tradeoffs discussed and other history not captured by code, tests. [1] https://git-scm.com/docs/git-interpret-trailers https://git-scm.com/docs/git-interpret-trailers

chickensong 5mo ago
A few questions: - Does Claude leverage the trailers automatically, or is usage initiated by you? - How often are you using the trailer lookups? - Any idea how this relates to token usage? If you're frequently busting cache on old sessions, it might be cheaper to read a local doc.
- bizzletk 5mo ago
  > Does Claude leverage the trailers automatically, or is usage initiated by you? Trailers hint is in my global CLAUDE.md so it knows: when debugging, saying something like "didn't we already discuss this in a previous session?" it will know what to look for. I also have a manually invoked `/search-session-transcripts` that I can use to natural-language inspect previous session by day, project, session id etc. Claude often uses this skill to narrow down on parts of the conversation that are relevant to the current query. > How often are you using the trailer lookups? Mondays are usually the day I need to refer to previous sessions from the week before. Trailer lookups are also good for continuing buildout of adjacent features. They've also been excellent in incident post-mortems where the PR text and commit message aren't enough to gauge the "how" of decisions that led to issues. > Any idea how this relates to token usage? I tested this. Session-transcripts are append-only so `/clear` and `/compact` don't clear out old messages, they stay stable and accessible. I also don't clean out my `~/.claude/sessions` ever so there's a lot in there, but the info is valuable and cheap.
  - chickensong 5mo ago
    Nice, thanks for sharing.

chickensong 5mo ago

A few questions: - Does Claude leverage the trailers automatically, or is usage initiated by you? - How often are you using the trailer lookups? - Any idea how this relates to token usage? If you're frequently busting cache on old sessions, it might be cheaper to read a local doc.

bizzletk 5mo ago
> Does Claude leverage the trailers automatically, or is usage initiated by you? Trailers hint is in my global CLAUDE.md so it knows: when debugging, saying something like "didn't we already discuss this in a previous session?" it will know what to look for. I also have a manually invoked `/search-session-transcripts` that I can use to natural-language inspect previous session by day, project, session id etc. Claude often uses this skill to narrow down on parts of the conversation that are relevant to the current query. > How often are you using the trailer lookups? Mondays are usually the day I need to refer to previous sessions from the week before. Trailer lookups are also good for continuing buildout of adjacent features. They've also been excellent in incident post-mortems where the PR text and commit message aren't enough to gauge the "how" of decisions that led to issues. > Any idea how this relates to token usage? I tested this. Session-transcripts are append-only so `/clear` and `/compact` don't clear out old messages, they stay stable and accessible. I also don't clean out my `~/.claude/sessions` ever so there's a lot in there, but the info is valuable and cheap.
- chickensong 5mo ago
  Nice, thanks for sharing.