[FEATURE] /insights: add --project or --cwd flag for project-scoped analysis

Resolved 💬 3 comments Opened Feb 24, 2026 by micradot Closed Feb 27, 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

/insights analyzes all Claude Code sessions globally across every project. for users working across multiple unrelated projects (e.g. home automation, business ops, SEO audits), the report blends everything together — making project-specific patterns hard to extract.

i run ~10 HA/bus-automation sessions alongside ~60 business/knowledge-management sessions. the insights report treats them as one body of work. the friction patterns, what-works observations, and suggestions are diluted by cross-project noise.

Proposed Solution

add a scoping flag to /insights:

/insights --project # scope to current project directory
/insights --cwd /path/to # scope to a specific working directory

match sessions by the cwd or project path recorded in session metadata. sessions outside that path are excluded from analysis.

this would let users get targeted insights per-project — friction patterns, feature suggestions, and workflow analysis that actually reflect how they use claude code in that specific context.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Performance and speed

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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