claude-code - 💡(How to fix) Fix /insights to allow filtering by project directory [1 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#56332Fetched 2026-05-06 06:30:56
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

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

I'm working on multiple projects at a time, and if i'm starting a new project where i go let's say 100 chats in, but i have other 10 projects with 10-20 times more chats, then the insights i'm receiving are no good for my current scope.

Allowing /insights to filter by project directory would be beneficial for everyone to understand and improve their CC workflows.

Proposed Solution

I'd like to be able to run /insights --project /path/to/working/project/dir and see generated insights based on sessions related to that project exclusively.

Alternative Solutions

tried deleting other sessions or moving them temporarily, but no help

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Implementing a --project flag for the /insights command to filter insights by project directory could address the issue.

Guidance

  • Investigate the current implementation of the /insights command to determine how it retrieves and processes session data.
  • Consider adding a --project flag to the /insights command to allow filtering by project directory.
  • Evaluate the feasibility of modifying the command to accept a directory path as an argument and use it to filter relevant sessions.
  • Assess the potential impact on performance and usability when filtering insights by project directory.

Example

No code snippet is provided due to lack of implementation details.

Notes

The proposed solution assumes that the /insights command can be modified to accept a directory path as an argument and filter sessions accordingly. The actual implementation may vary depending on the underlying architecture and data storage.

Recommendation

Apply workaround: Implement the proposed /insights command with a --project flag to filter insights by project directory, as it directly addresses the reported issue and improves productivity.

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…

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 /insights to allow filtering by project directory [1 participants]