session-log

Idle-aware hourly session logging detects file modifications since a stored timestamp marker and skips appending entries to daily markdown logs when no repository files have changed, preserving signal and avoiding clutter.

Session logging scans specified replication book files and .claude components, reads and compares file timestamps, and appends formatted hourly entries to a daily markdown log to track modifications during research or writing sessions.

Running a session close command produces end-of-session summaries suitable for insertion into a replication book chapter, aggregating modified files, decisions, and next steps from the daily markdown session log.

A session-logger agent is optional; the logging workflow can invoke the agent to produce human-readable summaries from hourly log entries, or append formatted entries directly to the daily markdown log.

Initialize a session timer to start tracking, call a periodic check command to compare file timestamps against a last-log marker, and update the marker each time new modifications are appended to the log.

Yes, the session logging workflow operates with no external dependencies, relying solely on reading file timestamps and appending entries to markdown files within your active project directory.