Session Chronicle FAQs

Question 1

What is session archaeology in Claude Code?

Accepted Answer

Session archaeology is the process of excavating Claude's local session logs to find the specific context, prompts, and subagent actions that led to a particular code change or architectural decision.

Question 2

What are the technical requirements for using this skill?

Accepted Answer

Session Chronicle requires jq for JSON parsing, brotli for log compression, the AWS CLI for S3 sharing, and the 1Password CLI (op) for secure credential injection.

Question 3

How does it handle auto-compacted sessions?

Accepted Answer

It identifies and links UUID chains across multiple sessions, allowing you to maintain a continuous thread of provenance even after Claude Code auto-compacts or starts a new session.

Question 4

Why does this skill track subagent sessions separately?

Accepted Answer

Subagent sessions (like those created by Explore or Plan agents) contain critical reasoning that is often lost when only the main session is tracked. Recording both ensures complete provenance.

Question 5

Does Session Chronicle commit large log files to my Git repository?

Accepted Answer

No. It follows a strict file ownership model where large artifacts are stored in gitignored directories or uploaded to S3, while only small, append-only registry files are committed to Git.

Session Chronicle

Key Features

Use Cases

Session Chronicle

Key Features

Use Cases