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

[arugina]

Description

After auto-updating to version 2.1.101, the /continue and /resume commands in the REPL now display sessions from all projects on the machine, regardless of which project directory Claude was launched from.

Previously, these commands were scoped to the current project directory — only sessions belonging to that project were shown.

Steps to Reproduce

1. Open a terminal in a specific project directory (e.g. ~/work/ganduri)
2. Run claude to start a session
3. Use /continue or /resume
4. Observe that sessions from all other projects are listed (e.g. ~/work/ps40, ~/work/wiki, etc.)

Expected Behavior

Only sessions belonging to the current project directory should be shown.

Actual Behavior

All sessions from all projects on the machine are shown in the picker.

Environment

• Claude Code version: 2.1.101
• OS: Linux Mint (Linux 6.17.0-20-generic)
• Install method: npm global (~/.npm-global)
• Updated at: approximately 2026-04-11 00:43 (auto-update)

Notes

The update timestamp on the binary (cli.js) matches the time the behavior changed — this appears to be a regression introduced in 2.1.101.

[davidlovas]

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.

[dreasan]

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