claude-code - 💡(How to fix) Fix [FEATURE] scope /insights command per project [1 comments, 2 participants]

Preflight Checklist

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

Problem Statement

(Same as #29844)

While helpful at a high-level, The /insights command currently aggregates data across all projects and sessions globally. For developers working across multiple projects — particularly those with different languages, frameworks, or domains — this produces noisy, low-signal output:

Suggestions and patterns from unrelated projects are mixed together, reducing relevance Project-specific recommendations (prompts, skills, hooks) lack the context needed to know where they apply or whether they'd transfer to another project Frequent context switching is required to mentally filter insights per project Recently inactive projects may be underrepresented or omitted entirely Stale suggestions from older sessions can surface even when the issue was resolved in a later session

Proposed Solution

Add an optional path argument to /insights as specified in #29844 or make the command project specific, it would also be helpful if claude code would maintain some files per project, instead of one global location, so its easier to access per project reports/context without post processing.

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Defer to #29844

Additional Context

Defer to #29844