Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /resume shows sessions from all directories instead of current directory (regression in 2.1.98-2.1.101) [1 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#46784•Fetched 2026-04-12 13:33:07
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
1
Author
shlomo-rshlomo-r
Participants
github-actions[bot]github-actions[bot]shlomo-rshlomo-r
Timeline (top)
labeled ×5commented ×1cross-referenced ×1subscribed ×1

The /resume command no longer scopes sessions to the current working directory. Instead, it shows sessions from all directories. This is a regression — the behavior worked correctly in v2.1.97.

Root Cause

The /resume command no longer scopes sessions to the current working directory. Instead, it shows sessions from all directories. This is a regression — the behavior worked correctly in v2.1.97.

Fix Action

Fix / Workaround

  • Rolling back to 2.1.97 immediately restores the correct per-directory scoping behavior
  • The regression likely relates to the worktree /resume fix introduced in v2.1.100 ("Fixed --resume from worktrees")
  • Workaround: downgrade to 2.1.97 via ln -sf ~/.local/share/claude/versions/2.1.97 ~/.local/bin/claude
RAW_BUFFERClick to expand / collapse

Bug Report

Description

The /resume command no longer scopes sessions to the current working directory. Instead, it shows sessions from all directories. This is a regression — the behavior worked correctly in v2.1.97.

Steps to Reproduce

  1. Have multiple Claude Code projects in different directories (each with their own sessions)
  2. cd into a specific working directory
  3. Start Claude Code and run /resume
  4. Expected: Only sessions from the current directory are listed
  5. Actual: Sessions from ALL directories are listed

Environment

  • Broken versions: 2.1.101 (confirmed), likely 2.1.98–2.1.100 as well
  • Working version: 2.1.97 (confirmed fix by rolling back)
  • OS: Linux (Ubuntu, kernel 6.8.0-107-generic)
  • Working directory type tested: non-git directory, and also git-initialized directory (both broken on 2.1.101)

Additional Notes

  • Rolling back to 2.1.97 immediately restores the correct per-directory scoping behavior
  • The regression likely relates to the worktree /resume fix introduced in v2.1.100 ("Fixed --resume from worktrees")
  • Workaround: downgrade to 2.1.97 via ln -sf ~/.local/share/claude/versions/2.1.97 ~/.local/bin/claude

extent analysis

TL;DR

Downgrade to version 2.1.97 to restore the correct per-directory scoping behavior for the /resume command.

Guidance

  • Verify the issue by following the steps to reproduce and checking the versions where the behavior is broken (2.1.101 and likely 2.1.98-2.1.100) and where it works (2.1.97).
  • To mitigate the issue, use the provided workaround: downgrade to 2.1.97 via ln -sf ~/.local/share/claude/versions/2.1.97 ~/.local/bin/claude.
  • Investigate the changes introduced in version 2.1.100, specifically the "Fixed --resume from worktrees" fix, as it is likely related to the regression.
  • Test the behavior in different directory types (non-git and git-initialized) to ensure the workaround or fix works consistently.

Notes

The provided workaround downgrading to 2.1.97 is a temporary solution. A more permanent fix would require identifying and addressing the root cause of the regression introduced in version 2.1.100.

Recommendation

Apply the workaround by downgrading to version 2.1.97, as it is a confirmed fix that restores the correct behavior, and the regression is likely related to changes introduced in later versions.

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…
#search optimization#API routing#API middleware#SSR setup#ISR setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING