Main
Use session-start/update/end as a lightweight project journal: the goal is continuity, not perfect documentation.
Keep sessions out of Git if you prefer: README suggests adding
sessions/to.gitignorewhen the log is personal or sensitive.Customize safely: start by adjusting paths/prefixes, then add team-specific commands once the core loop works.
Source-backed notes
- README documents six commands: session-start, session-update, session-end, session-current, session-list, session-help.
- README states commands use the
/project:prefix and store session state via a.current-sessionfile. - README includes a note on adapting to Claude Code's standard
.claude/commands/directory structure.
FAQ
- Where are sessions stored?: README uses a
sessions/directory plus asessions/.current-sessionpointer file by default. - Can I share sessions with my team?: Yes, but consider privacy. README suggests adding
sessions/to.gitignoreif you don't want it tracked. - Do these commands work outside Claude Code?: They are written for Claude Code's custom slash command system; other tools may need different wiring.