claude-code - 💡(How to fix) Fix Stats dashboard streak broken despite valid session data on disk [3 comments, 1 participants]

TL;DR

Update the stats dashboard to consider session content timestamps instead of relying solely on file metadata timestamps to accurately reflect active days.

Guidance

• Investigate how the stats dashboard currently determines active days and streaks, focusing on whether it uses file modification times (mtime) or actual session activity timestamps.
• Verify if the bulk-writing of session files (as suggested by the identical mtime values) is causing the discrepancy between the expected and actual behavior.
• Consider updating the dashboard to use a more robust method for determining active days, such as parsing session start/end timestamps from the JSONL files.
• Review the code responsible for updating the streak counter to ensure it correctly handles days with session activity, even if the sessions were bulk-written.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The solution may require changes to the stats dashboard's logic for determining active days and updating the streak counter. The identical mtime values for the session files on April 13 suggest that the issue might be related to how these files were written or updated.

Recommendation

Apply a workaround by updating the stats dashboard to use session content timestamps, as this approach is more likely to accurately reflect active days and maintain the correct streak counter.