Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] /insights report makes misleading productivity judgments from incomplete local-only data [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45282•Fetched 2026-04-09 08:09:00
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
VinaychalluruVinaychalluru
Participants
github-actions[bot]github-actions[bot]VinaychalluruVinaychalluru
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

The /insights report draws conclusions about a user's productivity based solely on local CLI session data, without disclosing that large portions of Claude usage are invisible to it. Specifically, it cannot see:

  • Sessions from claude.ai web (claude.ai/code or chat)
  • Claude Code sessions on other machines
  • Git commits and PR merges made outside a Claude Code CLI session on this machine
  • Commits pushed to GitHub repositories — even those made through Claude Code on another device, which should be retrievable via the GitHub API without requiring cross-machine file access

Despite these blind spots, the report generates statements like:

▎ "x sessions, y messages, zero commits — someone spent hours talking to Claude without shipping a single line"

This treats the absence of locally-detected commits as evidence of zero output. A user could have merged multiple PRs that week through Claude Code on another machine or via the web, and receive the same verdict.

What Should Happen?

Expected behavior:

At minimum, scope the language to what was actually measured: "0 commits detected in these 3 local CLI sessions." Do not draw productivity inferences beyond the data scope.

Beyond that, two improvements worth considering:

1. GitHub integration — since Claude Code already operates on git repositories, the report could optionally query the GitHub API for commits and PRs authored by the user, providing a more complete picture without requiring any cross-machine sync. 2. User-configurable data scope — allow users to opt in to cross-machine usage sync (e.g. via their Anthropic account), or at minimum display a visible disclaimer indicating what the report does and does not cover, so users can make informed decisions about how to interpret the data before acting on it.

Actual behavior: The report makes unqualified productivity claims using metrics it knows are incomplete, with no disclosure of data scope.

Error Messages/Logs

Steps to Reproduce

What's Wrong section is already updated with details.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.96 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

extent analysis

TL;DR

The /insights report should be modified to clearly indicate the scope of its data and avoid making unqualified productivity claims based on incomplete metrics.

Guidance

  • Modify the report to explicitly state what data it is based on, such as "0 commits detected in these 3 local CLI sessions", to avoid misleading conclusions.
  • Consider implementing GitHub integration to retrieve commits and PRs authored by the user, providing a more complete picture of productivity.
  • Add a user-configurable data scope or a visible disclaimer to indicate what the report does and does not cover, allowing users to make informed decisions.
  • Review the report's language to ensure it does not draw conclusions beyond the scope of the available data.

Example

No code snippet is provided as the issue does not contain sufficient technical details to generate a specific example.

Notes

The current implementation of the /insights report has never worked as expected, and the proposed changes aim to improve its accuracy and transparency.

Recommendation

Apply a workaround by modifying the report to clearly indicate its data scope and limitations, as a more comprehensive solution would require significant changes to the report's functionality and potentially the integration with the GitHub API.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#model loading#dependency error#configuration error#environment variable

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] /insights report makes misleading productivity judgments from incomplete local-only data [1 comments, 2 participants]