openclaw - 💡(How to fix) Fix [control-center] AI usage mix: Feishu sessions misclassified + stale data in cumulative view [1 participants]

TL;DR

Update the classifySessionTypeFromSessionKey and classifySessionTypeLabel functions to recognize Feishu and Webchat channel types, and modify buildSessionTypeBreakdownFromSessionContexts to use the full jsonl history events.

Guidance

• Update the classifySessionTypeFromSessionKey and classifySessionTypeLabel functions in usage-cost.ts to include Feishu and Webchat channel types, preventing them from being misclassified as "Main/内部会话".
• Modify buildSessionTypeBreakdownFromSessionContexts to use runtimeEvents30d instead of the sessions.json snapshot for the cumulative "all sessions" view.
• Verify the changes by checking the "AI usage mix (all sessions)" pie chart in the Control Center to ensure Feishu and Webchat sessions are correctly categorized and the cumulative view reflects the full 30-day token count.
• Review the byAgent and byProvider breakdowns to understand how they correctly utilize runtimeEvents30d and apply similar logic to buildSessionTypeBreakdownFromSessionContexts.

Example

// Example update to classifySessionTypeFromSessionKey
function classifySessionTypeFromSessionKey(sessionKey: string) {
  if (sessionKey.includes('feishu')) return 'Feishu';
  if (sessionKey.includes('webchat')) return 'Webchat';
  // Existing logic for cron, discord, and telegram
}

Notes

The provided solution assumes that the runtimeEvents30d contains the necessary information for the cumulative "all sessions" view. If this is not the case, additional modifications may be required.

Recommendation

Apply the workaround by updating the classifySessionTypeFromSessionKey and classifySessionTypeLabel functions and modifying buildSessionTypeBreakdownFromSessionContexts to use runtimeEvents30d, as this directly addresses the identified bugs and should provide the expected behavior.