claude-code - 💡(How to fix) Fix Expose session statistics in Stop hook [1 comments, 2 participants]

TL;DR

Implementing a session statistics exposure feature when the Stop hook fires will allow users to access and utilize key session metrics.

Guidance

• Identify the Stop hook event in Claude Code and determine the best approach to capture and calculate the required session statistics.
• Consider adding a callback function or an event listener to the Stop hook to collect and return the requested statistics, such as message counts, token usage, session duration, and file modifications.
• Evaluate the existing data structures and APIs in Claude Code to determine how to efficiently gather and provide the necessary statistics.
• Develop a data format or structure to organize and return the session statistics in a usable and accessible way for users.

Notes

The implementation details may vary depending on the specific architecture and design of Claude Code, and additional information about the codebase and its components may be necessary to provide a more comprehensive solution.

Recommendation

Apply workaround: Implement a custom solution to expose session statistics when the Stop hook fires, as this will allow users to access key metrics and build custom status reporting or analytics on session completion.