[FEATURE] Per-project insights reports (not just global)

Resolved 💬 2 comments Opened Feb 24, 2026 by pickatag Closed Feb 24, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

To Claude:
❯ Insights was a relly good function. BUT, a strange thing. I've been running two seperate projects that are really different and these insigths does not match them both. Shouldn't I get a specific insight for this project combined with a genereic insight that is relevant for all projects?

● That's a great observation. The insights report clearly skewed heavily toward your PDF catalog parsing project (22+ sessions) and only briefly mentioned ecom-auto (5 sessions), even though you're in the ecom-auto project right now. Getting a combined report across two very different projects makes the recommendations less actionable for either one.

This is a feature suggestion worth raising. The /insights command is relatively new, and per-project insights (or at least project-aware grouping) would be a natural improvement.

I'd recommend filing it at: https://github.com/anthropics/claude-code/issues

A good title might be: "Feature request: Per-project insights reports (not just global)" — explaining that when working across multiple unrelated projects, the insights blend together and lose relevance for the project you're actually in.

Proposed Solution

A per project section and a generic section. And the claude.md copies must be relevant for the project that I', in.

Alternative Solutions

_No response_

Priority

Low -

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗