One ai_logs folder for every session log and handoff, synced to Google Drive¶
- Date: 2026-11-06
- Status: Accepted
- Tags:
toolingstructureworkflow
Context¶
/compress and /handoff saved to whatever folder they were run from. In the vault, that was 0. PeriodicNotes/Session-Logs/. Everywhere else, it was a CC-Session-Logs/ folder in the project.
By 2026-11-06, the logs had spread across 11 folders:
- Copies: three identical copies in the larvis checkouts.
- Committed to repos: some were committed to git, in larvis and ai_tooling_foundations.
- Stale vault folder: the vault folder hadn't been written to since March, because most sessions start in project folders.
- Hard to find: finding the last handoff for a piece of work meant knowing which folder the session had started in.
Session logs and handoffs do different jobs. A session log is a searchable record of what happened. A handoff tells the next agent what to do.
Decision¶
All session logs and handoffs live in one folder outside every repo and outside the vault:
~/sandbox/ai_logs/
├── cc-session-logs/{project}/YYYY-MM-DD-{topic}.md
└── handoffs/{project}/YYYY-MM-DD-handoff-{topic}.md
{project}:lifeosinside the vault- otherwise the basename of the git top-level folder
- otherwise the basename of
pwd - Skills:
/compressand/handoffalways write there, and/resumeand/weekly-reviewread from there. - Sync: Google Drive watches
ai_logsand nothing else. - work-tracker hook:
~/sandbox/ai_logsis exempt, asCC-Session-Logs/was, so writing a log never counts as untracked work. Samecounts_as_changeexemption list. - Migration on 2026-11-06:
- Moved: logs that weren't committed anywhere.
- Copied, originals left in place: logs committed to larvis and this repo, and the vault's
Session-Logs/. Your rule is never to delete vault files, and older/resumehistory lives there.
Alternatives Considered¶
| Option | Why Rejected |
|---|---|
Keep per-project CC-Session-Logs/ |
That's the sprawl this fixes, and logs end up committed to repos. |
Vault 0. PeriodicNotes/Session-Logs/ for everything |
Mixes agent transcripts into the knowledge vault, and the vault already has its own sync. |
| One flat folder | Session logs and handoffs serve different readers, and a per-project subfolder keeps where each came from. |
Consequences¶
Positive:
- One place to search, back up and sync. The next handoff is always in
ai_logs/handoffs/{project}/. - No more session logs committed to project repos.
Negative / Trade-offs:
- Logs are no longer next to the code they describe.
- The copies committed to larvis and ai_tooling_foundations, and the vault's
Session-Logs/, still exist and will drift fromai_logs. Remove them from those repos when convenient. ~/.claude/commands/*.mdandskills/handoffwere edited live. The weekly harness mirror (ADR 0033) brings them intoclaude/harness/.