claude-code - 💡(How to fix) Fix Filter /resume history by current 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#48049Fetched 2026-04-15 06:34:45
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×2closed ×1
RAW_BUFFERClick to expand / collapse

Problem

When using /resume, it shows all recent conversations across every project globally. If I work on multiple projects throughout the day, the resume list becomes cluttered with conversations from unrelated projects, making it harder to find the one I want to continue.

Expected Behavior

/resume should filter conversations by the current working directory (project), showing only conversations that were started in the same project. The conversation data is already organized by project path internally (~/.claude/projects/<path-based-dir>/), so the filtering info is already available.

Suggested Approach

  • Default /resume to show only conversations from the current project
  • Optionally, add a flag like /resume --all to show the global list when needed

This would make /resume much more useful in multi-project workflows.

extent analysis

TL;DR

Modify the /resume command to filter conversations by the current working directory, showing only conversations from the same project by default.

Guidance

  • Review the current implementation of the /resume command to understand how it retrieves conversation data from the ~/.claude/projects/<path-based-dir>/ directory.
  • Update the command to use the current working directory to filter conversations, utilizing the existing project path organization.
  • Consider adding an optional flag (e.g., /resume --all) to allow users to view the global conversation list when needed.
  • Test the updated /resume command with multiple projects to ensure it correctly filters conversations by project.

Example

# Example of how the updated /resume command could be implemented
/resume {
  # Get the current working directory (project)
  project_dir = $(pwd)

  # Filter conversations by project directory
  conversations = $(find ~/.claude/projects/ -name "${project_dir}" -print0 | xargs -0 -I {} sh -c "cat {}/*.conversation")

  # Display the filtered conversations
  echo "${conversations}"
}

Notes

The suggested approach assumes that the conversation data is properly organized by project path in the ~/.claude/projects/<path-based-dir>/ directory. If the data is not correctly organized, the filtering may not work as expected.

Recommendation

Apply the workaround by modifying the /resume command to filter conversations by the current working directory, as this will provide the desired functionality and improve the user experience in multi-project workflows.

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 Filter /resume history by current project directory [1 participants]