claude-code - 💡(How to fix) Fix Feature: Expose token counts and cost in session/hook lifecycle [2 comments, 3 participants]

TL;DR

Implementing a SessionEnd hook with token and cost data or enriching existing hooks with this information can unblock the development of session analytics and cost dashboards.

Guidance

• To address the issue, consider implementing one of the proposed solutions: SessionEnd hook, enriching existing hooks, or creating a session metadata API.
• Evaluate the trade-offs between these options, such as the complexity of implementation and the frequency of data updates required for your use case.
• When choosing an approach, consider the specific requirements of your application, including the need for real-time data updates and the potential impact on system performance.
• Ensure that the chosen solution provides the necessary data, including tokens_in, tokens_out, and cost_usd, to support the desired analytics and cost tracking features.

Example

{
  "session_id": "...",
  "tokens_in": 24000,
  "tokens_out": 8000,
  "cost_usd": 0.35,
  "duration_seconds": 720,
  "turn_count": 8
}

This example payload illustrates the data that could be provided by a SessionEnd hook to support session analytics and cost tracking.

Notes

The choice of solution will depend on the specific requirements of your application and the constraints of the Claude Code CLI and daemon architecture. It is essential to evaluate the potential impact on system performance and the complexity of implementation when selecting an approach.

Recommendation

Apply a workaround by implementing the SessionEnd hook, as it is the preferred option and provides a clear and straightforward solution to the problem. This approach allows for the collection of necessary data for session analytics and cost tracking without modifying existing hooks or introducing a new API endpoint.