📌 Hi**! I’m Hahaseon. I share simple ways to use AI in your work and personal notes.**
This guide walks you through the session logging system I use, so you can set it up for yourself.
You are welcome to copy the material to install it in your own environment. However, unauthorized adaptation, redistribution, and commercial sale are prohibited. If you try it, please send me a direct message with your results or feedback. It helps me create future resources. Feel free to message me with any setup questions, too ✨
AI Creator Hahaseon (@hahaseonha.ai)
The 30-Second Summary
/session-wrap: Saves what you did, learned, got stuck on, and plan to do next in a single conversation session as a Markdown file, a plain-text document with simple formatting.
/daily-wrap: Brings together the day’s session notes to identify repeated mistakes and tasks worth automating.
- The default save locations are
~/Documents/Session Wraps and ~/Documents/Daily Wrap.
- With the optional hooks installed, a session is added to a pending queue when it ends. The next time you start or resume Claude Code, you will be notified about sessions that still need a wrap-up. A hook is a script that runs when a specified event occurs.
- There is no separate code that sends the raw conversation to an external server. However, Claude Code reads the local transcript, or conversation log, to summarize it, so be sure to exclude sensitive conversations.
Who This Is For
- People who often forget what they did with Claude Code by the next day
- People who want to automatically document trial and error and lessons learned
- People who want a daily view of whether they are repeating the same mistakes
- People looking for the right time to turn recurring tasks into reusable skills or automations
- People who keep work journals in Obsidian or Markdown
How It Works