/continue and /resume show all sessions across projects instead of current project only (regression in 2.1.101)

Strongly agree — hit this today after upgrading to 2.1.101 and it's a significant workflow regression.

Project-scoped session history is the entire reason I run claude --resume from a specific project directory in the first place. Having to hit Ctrl+A every single time to filter down to the current project defeats the purpose of launching from the project directory at all, and risks accidentally opening an unrelated session from a completely different codebase with its own build state, memory, and context.

Requests:

1. Revert the default so --resume / /resume scope to the current project directory, as they did pre-2.1.101.
2. If there's genuinely demand for a global view, make it an opt-in flag (--resume --all) or a persistent config setting — not the new default.
3. At minimum, make the default configurable via settings.json so users can pick their own behavior without keypresses on every invocation.

The Ctrl+A hint at the bottom of the picker shows the filtering already exists — it's just inverted from what most users actually want.

It's an unreasonable change that creates friction, unfortunately. Needs to be configurable at minimum.

How you even allow this kind of stuff to happen? 🤦‍♂️ Same.. very annoying!

Experiencing this as well. The previous project-scoped behavior was much more useful — showing all sessions globally makes it hard to find the one you need, especially when working across multiple repos.

Additionally, there's no way to search or filter by project path in the picker, which compounds the problem. A search/filter option or a config to scope /resume back to the current project directory would be appreciated.

Just downgraded to 2.1.100 and everything got back to normal

Yeah, downgrading seems the only option ATM, if native, you might have the previous version in $HOME/.local/share/claude/versions.. or you can install a specific version via everyones favourite way of installing things, curl:

curl -fsSL https://claude.ai/install.sh | bash -s 2.1.100

You can also grab it from the URL for your OS like https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.100/darwin-arm64/claude

note, the curl script seems to clear versions out the versions directory, not sure what the cleanup process is..

This is a terrible change! Please reverse it or give us a setting to opt out and back into the old behavior. I have 10+ projects going and every one is noisy and hard to find things in now.

Please make the default configurable. I understand 'ctrl-A' will filter it but the note at the bottom clearly is not obvious. This change happened to correspond with me moving history from one directory to another and I thought it had broken things. It took me pasting what it was displaying into claude for claude to point out the ctrl-A a the bottom.

Like others it sounds like, I use claude on multiple projects that have nothing to do with one another and I am hard pressed to see why this would ever be useful as a default setting.

Can ya'll PLEASE put these changes behind OPT-IN feature flags?

Ya'll wouldn't need to block people from using 3rd party coding agents if ya just stopped with the slop releases on Claude Code (people are looking for more stable options). CC is a great product and still one of the best agents, but I'm losing trust that it can remain stable.

I don't mind changing my workflow constantly if it means getting better results (it generally does), but changes like this are just wild for a company that is aiming to be the enterprise solution in the LLM space.

I love Anthropic's models and don't want to swap providers, but every day it's getting harder to justify staying. I'm very tempted to move to Codex just for the stability. Please give me a reason to stay.

...I'm concerned that the next major supply chain hack after the litellm one will be Claude Code if changes like this aren't handled properly

Same issue here. Windows 11, Claude Code v2.1.104.

I have 25+ project directories under ~/.claude/projects/ organized by department (n8n automation, web dev, blockchain, client projects by country, etc.). Before 2.1.101, /resume only showed sessions from the current project — which was the correct behavior for my workflow.

Now it shows ALL sessions from ALL projects mixed together, making it very difficult to find the right session. I manage 10+ active client projects simultaneously, each with their own folder and sessions.

Expected behavior: /resume should default to showing only sessions from the current project directory, with an option to search across all projects if needed.

Current behavior: Shows all sessions from all 25 projects mixed together.

This is a significant regression for users who rely on project isolation. Please consider reverting to the previous scoped behavior as the default, or at minimum adding a filter/toggle.

I am having exact same issue. I am glad I am not alone. I am going to downgrade.

I work across multiple directories concurrently and used to rely on /resume to maintain my Claude instances. However, due to the recent patch, the simple action of just typing /resume and hitting Enter to switch now requires me to manually match and search for the exact directory names. This is an absolutely terrible workflow.

+1 on this regression. After updating to 2.1.101, /resume now lists sessions from all my projects, making it harder to quickly find the session I need for the current project.
Agree with @davidlovas — the previous project-scoped default was the right behavior. If a global view is useful for some users, it should be opt-in (e.g. --all flag or a settings.json toggle), not the default.

IMHO the Ctrl-A in the session picker should "turn on" the global session picker and the default should be to show project only sessions.

I thought I had broken my claude history and was polluting one project with another. This is a really bad change.

+1 on this regression. The cross-project resume list is actively painful for anyone with more than a handful of projects.

My workflow: I cd into a project and run claude --resume expecting to pick up where I left off on that project. Instead I get a mixed list of sessions from every directory I've ever worked in, most of which are irrelevant to
what's in front of me right now. Finding the right one means scanning project paths in the picker every single time.

The old behavior (scope to current working directory) was the right default because the current directory is a strong signal of intent — I'm already in the project, so that's clearly what I want to resume. If the intent is to
let users also browse cross-project sessions, please make that opt-in via a flag (e.g. --resume --all) rather than the default.

Proposed fix:

• Default: claude --resume lists sessions for the current project only (match by cwd → ~/.claude/projects/<project-hash>/)
• Opt-in: claude --resume --all to list sessions across all projects

Happy to use a workaround in the meantime, but this is noticeably worse ergonomics than 2.1.100

Quick solution until issue is fixed: npm install -g @anthropic-ai/claude-code@2.1.100

+1 on this regression. Adding a data point that shows how much worse this gets when combined with the hard 50-session cap (#35698).

I have ~1600 sessions across 57 project directories on Windows, accumulated over several months. Before 2.1.101, /resume scoped per project worked fine — every project had its own independent history, 50 sessions per project was almost always enough. After 2.1.101 the global mtime-ordered top-50 list means entire projects are now completely invisible, not just harder to find. In my case a project with ~10 sessions I actively use (D:\PHD) shows zero entries in /resume because other projects have more recent activity that fills the 50 slots. Ctrl+A doesn't help because the filter operates on the already-loaded 50, not on the full per-project scan — so the project-scoped view returns empty even though the sessions physically exist on disk.

The only reliable way to reach older sessions right now is claude --resume <session-id> from the command line, which requires knowing the UUID up front. That's not a UI.

Two bugs multiplying each other:

1. The 2.1.101 regression (this issue) — global instead of per-project
2. The hardcoded 50-session cap (#35698) — fine when per-project, catastrophic when global

Fixing either one independently would help, but fixing #46445 (revert to per-project default) is the higher-leverage fix because it preserves the 50-cap's original assumption (50 per project, which was ample).

Strongly support the proposed fix in the thread: default to current-project scope, make cross-project an opt-in flag (--resume --all) or Ctrl+A toggle with inverted semantics. The current default actively hides data users are trying to reach.

Downgrading to 2.1.100 until this is fixed.

Same problem here. Need to find a previous session, and it is not available within the 50 limit.

Same issue, frustrating! thankfully I have my own /search-sessions skill that can resolve this, but it is annoying.

quick fix is in the resume picker hit ctr + a and it'll scope it to the current folder

2.1.105 dropped and still no fix for this

Still reproducible on v2.1.107 across two machines:

| Machine | OS | Claude Code version |
|---------|-----|---------------------|
| Lenovo Legion Y9000P | WSL2 (Ubuntu 24.04.4 LTS) | 2.1.107 |
| MacBook Air | macOS | 2.1.107 |

Behavior: /resume shows sessions from all project directories, not just the current working directory. This makes it very difficult to find the correct session to resume when working across multiple projects.

Expected: /resume should only list sessions belonging to the current project directory, as it did before the regression.

This was not fixed in 2.1.104 or 2.1.107 — the issue persists across both Linux and macOS.

Fixed in 2.1.108

• Improved /resume picker to default to sessions from the current directory; press Ctrl+A to show all projects

Fixed in 2.1.108 * Improved /resume picker to default to sessions from the current directory; press Ctrl+A to show all projects

However, /resume still recommends other directories along with it, causing confusion.

> Fixed in 2.1.108 > > * Improved /resume picker to default to sessions from the current directory; press Ctrl+A to show all projects However, /resume still recommends other directories along with it, causing confusion.

interesting...it doesn't do that for me. I have to hit Ctrl+A to see other dirs now (expected behavior)

> > Fixed in 2.1.108 > > > > * Improved /resume picker to default to sessions from the current directory; press Ctrl+A to show all projects > > > However, /resume still recommends other directories along with it, causing confusion. interesting...it doesn't do that for me. I have to hit Ctrl+A to see other dirs now (expected behavior)

I am experiencing an issue where session history from other directories is exposed in the autocomplete suggestions. This is reproducible in Claude Code v2.1.108 on Windows.

1. Run claude.
2. Type /res and press the Tab key.
3. Recent session history from all directories, not just the current one, is exposed. <- I expect only the session history from the current directory to be displayed.

All fixed for me now. Although I think if I have accidentally opened the wrong session in a directory it still loads from that directory and I will have to fix as I go by CTRL +A and selecting the right one.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.