Tab · History
Sessions
Walk in oriented every morning. The end-of-session journal is the night-shift handoff — what got built, what's next, what slowed us down. Hand-written, distinct from the Activity ledger's telemetry sessions (so the counts differ on purpose).
See it in motion
Where to find it
- Localhost:
/sessions.html?repo=<id> - On disk:
.claude/brain/sessions/YYYY-MM-DD-<slug>.md - Keyboard: ⌘ K then
sessions - Sidebar: History → Sessions
What it does for you
Cold-start tomorrow in two minutes.Yesterday's “What's next” line is tomorrow's opening move. No re-derivation, no re-reading the diff to remember where you stopped.
Async standup without the meeting.A teammate appended last night? New-since-last-visit dot tells you. Read the entry, skip the daily.
The friction line compounds.The “what slowed us down” bullet is where errors.md, anti-patterns.md, and patterns.md get their entries. The brain learns from journals, not memory.
Configure
No config — just the filename convention and three sections. Sessions are hand-written by whoever ran the session; the tab is a reverse-chronological index with substring search.
Use it well
Five minutes at session end, every time. Three sections: What got built (bullets + file paths) · What's next (one immediate action) · What slowed us down (the meta line). Commit it in the same PR as the change. Read the previous entry at session start — that's the minimum re-orientation.