/insights report shows stale February data instead of recent March sessions

Bug Description

The /insights command generates a report based on stale data (February 10 – March 14 period showing mostly February sessions) instead of reflecting recent March 10–14 activity.

Running /insights on March 14, 2026 produced a report that heavily references February work and projects (e.g., "92 sessions over one month" referencing Feb 10–Mar 14) but doesn't capture the current day's session patterns or recent March activity accurately. The report header says "2026-02-10 to 2026-03-14" but the analysis narrative and project areas are weighted toward older February data.

Expected Behavior

The /insights report should include recent sessions (March 10–14) in its analysis, reflecting current workflow patterns and projects.

Actual Behavior

Report appears to be generated from a stale analytics snapshot. Recent sessions from March 10–14 are either missing or underrepresented in the analysis.

Context from Anthropic Support (Fin AI Agent)

Claude Code analytics data has a 3-day delay — March 14th data wouldn't be available until March 17th. However, since you're seeing February data instead of the expected March 10-11 data (which should be available by now), this suggests a potential data pipeline issue. The analytics system runs daily aggregation at 10:00 UTC and makes data available three days later. Since you're running version 2.1.76 (well above the minimum 2.0.28 required for analytics), the version isn't the problem.

Support recommended filing via /bug for internal investigation of a possible data pipeline failure.

Environment

• Claude Code version: 2.1.76
• OS: macOS (Darwin 25.3.0)
• Shell: zsh
• Platform: darwin