Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /resume command no longer filters conversations by current directory [2 comments, 2 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#46752•Fetched 2026-04-12 13:33:59
View on GitHub
Comments
2
Participants
2
Timeline
8
Reactions
0
Author
jpenberthyjpenberthy
Participants
github-actions[bot]github-actions[bot]jpenberthyjpenberthy
Timeline (top)
labeled ×4commented ×2closed ×1cross-referenced ×1

When running claude from a specific project directory and using the /resume command, the conversation picker now shows all conversations across all projects instead of only conversations from the current working directory.

Previously, /resume would filter the list to only show conversations that were started in the current directory, which was the expected and more useful behavior.

Root Cause

When running claude from a specific project directory and using the /resume command, the conversation picker now shows all conversations across all projects instead of only conversations from the current working directory.

Previously, /resume would filter the list to only show conversations that were started in the current directory, which was the expected and more useful behavior.

RAW_BUFFERClick to expand / collapse

Description

When running claude from a specific project directory and using the /resume command, the conversation picker now shows all conversations across all projects instead of only conversations from the current working directory.

Previously, /resume would filter the list to only show conversations that were started in the current directory, which was the expected and more useful behavior.

Steps to Reproduce

  1. cd into a specific project directory
  2. Run claude
  3. Use /resume
  4. Observe that conversations from all project directories are listed, not just the current one

Expected Behavior

/resume should only show conversations associated with the current working directory, matching the previous behavior.

Actual Behavior

/resume shows all conversations regardless of which directory they were started in.

Environment

  • Claude Code version: 2.1.101
  • OS: Linux Mint 22.3 (Cinnamon)
  • Shell: bash

Notes

claude -c (continue) still correctly respects the current directory context and resumes the most recent conversation for that directory. The issue is specifically with the /resume interactive picker.

🤖 Generated with Claude Code

extent analysis

TL;DR

The issue can be mitigated by modifying the claude command to respect the current working directory when using the /resume command.

Guidance

  • Verify that the claude version 2.1.101 is the latest available, as this issue may be resolved in a newer version.
  • Check the documentation for claude to see if there are any configuration options or flags that can be used to filter conversations by directory.
  • Test using claude -c instead of /resume to see if it meets the required functionality, as it correctly respects the current directory context.
  • Consider reporting this issue to the claude developers, as it appears to be a regression from the previous behavior.

Notes

The cause of this issue is unclear, but it may be related to a change in the claude codebase that affects the /resume command's filtering behavior.

Recommendation

Apply workaround: Use claude -c instead of /resume to resume the most recent conversation for the current directory, as it still respects the current directory context.

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…
#tool integration#LLM response#prompt template#agent execution#callback error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING