← all repositories
iannuttall/claude-sessions

Teaching Claude to take its own meeting notes

A set of slash commands that turns Claude Code into its own project historian, logging decisions and progress across chat sessions.

1.2k stars Coding Assistants
claude-sessions
Not currently ranked — collecting fresh signals.
star history

What it does This repo is a collection of markdown command files that add /project:session-* slash commands to Claude Code. Instead of treating each chat as a disposable conversation, you get a structured workflow: start a named session, append timestamped updates, and end with a generated summary. Everything lands as plain markdown files in a local sessions/ directory, tracking git changes, todos, and implementation notes as you go.

The interesting bit The clever part isn’t just logging—it is using Claude itself as the stenographer. Because these commands are essentially elaborate prompts, Claude writes its own session history, capturing context that would otherwise vanish when the context window resets. Future sessions can read these logs instead of re-analyzing the entire codebase from scratch.

Key highlights

  • Six command files (session-start, session-update, session-end, session-current, session-list, session-help) that drop into a commands/ folder
  • Auto-captures git status, todo progress, and problems solved without manual templating
  • Stores everything as timestamped local markdown, making history searchable and diffable
  • Optional auto-summarization when you run updates without providing custom notes
  • Adaptable to Claude Code’s standard .claude/commands/ path or other AI assistants (with tweaks)

Caveats

  • This is structured prompt engineering, not a plugin or executable: the “commands” are markdown files containing instructions for Claude to interpret
  • The README’s troubleshooting section flags practical rough edges—session tracking fails if the .current-session file is missing or permissions are wrong, and git integration only works inside initialized repositories
  • Requires manual discipline; the system will not force you to start or end sessions

Verdict Worth a look if you treat Claude Code as a long-term pair programmer and are tired of re-explaining your codebase every morning. Skip it if you want an automated, IDE-integrated tool—this demands the discipline to actually stop and log your progress.

Frequently asked

What is iannuttall/claude-sessions?
A set of slash commands that turns Claude Code into its own project historian, logging decisions and progress across chat sessions.
Is claude-sessions open source?
Yes — iannuttall/claude-sessions is open source, released under the MIT license.
How popular is claude-sessions?
iannuttall/claude-sessions has 1.2k stars on GitHub.
Where can I find claude-sessions?
iannuttall/claude-sessions is on GitHub at https://github.com/iannuttall/claude-sessions.

heatdrop uses Google Analytics to see which pages get read — nothing else. Your call. How we handle data.