[FEATURE] Setting to persist default --resume picker scope per user

Just found out and it's difficult to what find current project's chats. Did you find any fix?

Yes .. i mentioned it ..Press CTRL+A then it shows only the projects resumes...but no permanent yet without doing a work around

Didn't work for me. When I press CTRL+A it shows no results. I can't believe instead of improving with user feedbacks, anthorpic is downgrading their products and services.

it says under them all what to press .. mac is ctrl * A windows might be different

Sent via mobile email
[Tech Support]<https://www.corsolutions.co.uk/> [Content Writing] <https://web-smart.co/website-content-writing/> [Web Design] <https://web-smart.co/> [Book a Meeting] <https://appt.link/meet-with-pete-gypps/chat-with-pete-R9wR8KNd>
[Email Footer]

________________________________
From: Moazam @.*>
Sent: Sunday, April 12, 2026 3:47:49 PM
To: anthropics/claude-code @.*>
Cc: Pete Gypps @.>; Author @.>
Subject: Re: [anthropics/claude-code] [FEATURE] Setting to persist default --resume picker scope per user (Issue #46549)

[https://avatars.githubusercontent.com/u/5168122?s=20&v=4]moazam1 left a comment (anthropics/claude-code#46549)<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4231731665>

Didn't work for me. When I press CTRL+A it shows no results. I can't believe instead of improving with user feedbacks, anthorpic is downgrading their products and services.

—
Reply to this email directly, view it on GitHub<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4231731665>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5GYU4VSAAURRN4QVTUVF5L4VOUBLAVCNFSM6AAAAACXUXBDFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZRG4ZTCNRWGU>.
You are receiving this because you authored the thread.Message ID: @.***>

I would suggest opening another and checking if its the same .. then if it is ask claudecode itself why there are no resumes
also give this to one of your claudes and it should be able to check
Why Ctrl+A shows empty

When they press Ctrl+A (filter to current directory), the picker looks at:

getProjectDir(canonicalizePath(cwd))

It'll be empty if any of these are true:

1. They're in a different cwd than where they created sessions. Sessions are keyed to the EXACT canonical path. Running claude from /Users/john/my-project/src/ is a different project dir than

/Users/john/my-project/. Different folder = different sessions list.

1. They moved or renamed the project folder. Old sessions are stored under the old sanitized path. New cwd produces a new sanitized path. The old sessions are still on disk but invisible from the new

path.

1. Symlink resolved differently. canonicalizePath uses realpath which resolves symlinks. If they cd via a symlink but sessions were created via the real path (or vice versa), the paths don't match.
2. They genuinely haven't created sessions from this exact directory yet. First time in this cwd = no sessions.

How to check manually

They can run:

# What Claude Code thinks your project dir is:
echo ~/.claude/projects/$(pwd | tr -c 'a-zA-Z0-9' '-')

# Does it exist? What's in it?
ls ~/.claude/projects/$(pwd | tr -c 'a-zA-Z0-9' '-')/*.jsonl 2>&1

# How many total sessions across ALL projects?
find ~/.claude/projects -name "*.jsonl" | wc -l

# Which project dirs have sessions?
for d in ~/.claude/projects/*/; do
count=$(ls "$d"*.jsonl 2>/dev/null | wc -l)
[ "$count" -gt 0 ] && echo " $count sessions: $(basename $d)"
done

I have started several sessions but the issue is it always show empty list. Tried another PC and have same issue. It could be OS specific issue.

If it’s windows and not Mac then what does it say at the bottom of the global list of resumes?
There was also a change to windows pcs that they warned about a month ago.

Just talk to your claude and get it to scan the changelog of the claudecode repo that we are at now
Tell it to look for the solution to your problems

From: Moazam @.*>
Date: Sunday, 12 April 2026 at 18:21
To: anthropics/claude-code @.*>
Cc: Pete Gypps @.>, Author @.>
Subject: Re: [anthropics/claude-code] [FEATURE] Setting to persist default --resume picker scope per user (Issue #46549)

[https://avatars.githubusercontent.com/u/5168122?s=20&v=4]moazam1 left a comment (anthropics/claude-code#46549)<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4232041546>

I have started several sessions but the issue is it always show empty list. Tried another PC and have same issue. It could be OS specific issue.

—
Reply to this email directly, view it on GitHub<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4232041546>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5GYU4QM54IXGLMEGC7XFRD4VPGCVAVCNFSM6AAAAACXUXBDFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZSGA2DCNJUGY>.
You are receiving this because you authored the thread.

I see this:

Ctrl+A to only show current directory · Ctrl+B to only show current branch · Space to preview · Ctrl+R to rename · Type to search · Esc to cancel ·

This happened about a week ago I might have to rollback to previous version until this issue annoying issue is resolved.

new keyboard hehe .. or get claude to fix itself as mentioned

Sent via mobile email
[Tech Support]<https://www.corsolutions.co.uk/> [Content Writing] <https://web-smart.co/website-content-writing/> [Web Design] <https://web-smart.co/> [Book a Meeting] <https://appt.link/meet-with-pete-gypps/chat-with-pete-R9wR8KNd>
[Email Footer]

________________________________
From: Moazam @.*>
Sent: Sunday, April 12, 2026 6:39:01 PM
To: anthropics/claude-code @.*>
Cc: Pete Gypps @.>; Author @.>
Subject: Re: [anthropics/claude-code] [FEATURE] Setting to persist default --resume picker scope per user (Issue #46549)

[https://avatars.githubusercontent.com/u/5168122?s=20&v=4]moazam1 left a comment (anthropics/claude-code#46549)<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4232093630>

I see this:

Ctrl+A to only show current directory · Ctrl+B to only show current branch · Space to preview · Ctrl+R to rename · Type to search · Esc to cancel ·

This happened about a week ago I might have to rollback to previous version until this issue annoying issue is resolved.

—
Reply to this email directly, view it on GitHub<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4232093630>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5GYU4TNWY24VLL7QJMKZU34VPIDJAVCNFSM6AAAAACXUXBDFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZSGA4TGNRTGA>.
You are receiving this because you authored the thread.Message ID: @.***>

+1 on this. Hit the exact same regression on 2.1.104 and was genuinely confused — thought something in my config broke before I found the changelog entry.

A few things worth adding to the case for a persisted setting:

1. The "fix" framing is misleading. The 2.1.101 changelog describes the old narrow default as a bug ("hiding sessions from other projects"). But for anyone with more than a handful of projects in ~/.claude/projects/, cwd-scoped was never a bug — it was the whole point. Calling one camp's preference a "bug" and silently flipping the default on everyone is how you get surprised users.

1. Ctrl+A every time is not a workaround, it's a tax. Muscle memory for /resume → arrow → enter now routinely lands on the wrong project's session. The cost isn't the extra keystroke, it's the attention budget spent re-checking the picker every time.

1. The infrastructure already exists. 2.1.98 added filter hint labels with project/worktree/branch in the indicator. All that's missing is a single settings.json key to pick which filter is active on open. This is a ~10 line change, not a design overhaul.

1. Prior art suggestion: mirror how git log handles --all — default is scoped, --all widens. Nobody filed bugs claiming git log "hides commits from other branches."

Happy with whatever key name — resume.defaultScope, resumePickerDefaultScope, resume.filterByCurrentProject — just please make it stick.

This was an intentional change. we have got a lot of feedback for folks not finding sessions. This is why V2.1.100 flipped the defaults. To filter current project use Ctrl+A and to filter only current worktree use Ctrl+T

Prior art suggestion: mirror how git log handles --all — default is scoped, --all widens. Nobody filed bugs claiming git log "hides commits from other branches."

Would love to here how others feel about this as well

+1 — @mhegazy pointed me here from #46784. Adding one workflow variant not yet covered:

I run one terminal window per project (parallel, each cd'd into its own repo), so --resume wasn't just "find a session" — it was the navigation primitive that made multi-project work fast. Each window's picker was a pre-scoped list by design of the workflow. Post-change, every window opens the same ~50+ global list with other projects as distractors, and Ctrl+A restores the right view but has to be re-triggered per window per invocation.

@mkll's "attention tax" framing is exactly right: the cost isn't the keystroke, it's re-scanning a picker that used to be pre-scoped. Happy with any spelling — resume.defaultScope, resumePickerDefaultScope, whatever — just please persist it.

its regression ..and why is it hardcoded..wheres the setting that would allow you to chose defaults... ive loved claudecode since the beginning and have multiple max accounts but companies dictating how we work on a product like this when it could be a switch only further forces us all to make our own harnesses and local models without the stupidy !

This was an intentional change. we have got a lot of feedback for folks not finding sessions

Well, I suppose those folks not finding projects too. :)

But that’s not what the resume issue was and finding global projects is not the fix ..thats dumb… if they cant find sessions they are dumb too ! . .

1.
Claudecode cli gets confused if it works on too many projects (we know this) and that’s even with a switcher I built, that just sometime have meltdown and do the wrong thing and yes even with skills.
2.
Claudecode cli sessions should be per project or per client
3.
If the above is true, then why the hell would anyone want to open their cli in the project root and type claude —resume and be presented with every other projects resume ! Why !! That’s not speed, thats not smart an it surely isn’t what I expect of anthropic.

From: Alex Sherbakov @.*>
Date: Monday, 13 April 2026 at 18:23
To: anthropics/claude-code @.*>
Cc: Pete Gypps @.>, Author @.>
Subject: Re: [anthropics/claude-code] [FEATURE] Setting to persist default --resume picker scope per user (Issue #46549)

[https://avatars.githubusercontent.com/u/1652009?s=20&v=4]mkll left a comment (anthropics/claude-code#46549)<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4238328239>

This was an intentional change. we have got a lot of feedback for folks not finding sessions

Well, I suppose those folks not finding projects too. :)

—
Reply to this email directly, view it on GitHub<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4238328239>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5GYU4SIP3UWJN4DZ4BQHU34VUO73AVCNFSM6AAAAACXUXBDFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZYGMZDQMRTHE>.
You are receiving this because you authored the thread.

@mhegazy
There's no single "_right_" approach — people are different, everyone has their own habits, established practices, and working styles, and I fully allow for, and have no doubt, that there are people who are used to dealing with a pile of different projects in one directory and a pile of different sessions in one picker, and they just find what they need via search.

But not everyone is like that. There's a large number of people accustomed to order, separation, and organization.

And, frankly, an approach that implies separation and organization is more deserving of being the default than a "free-for-all" and a "jumbled heap."

That said, neither approach should or can be mandatory or imposed, and neither of them should be the default for everyone. The default should be chosen and saved by the user.

Absolutely and exactly what I was saying.

From: Alex Sherbakov @.*>
Date: Monday, 13 April 2026 at 18:33
To: anthropics/claude-code @.*>
Cc: Pete Gypps @.>, Author @.>
Subject: Re: [anthropics/claude-code] [FEATURE] Setting to persist default --resume picker scope per user (Issue #46549)

[https://avatars.githubusercontent.com/u/1652009?s=20&v=4]mkll left a comment (anthropics/claude-code#46549)<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4238387781>

@mhegazy<https://github.com/mhegazy>
There's no single "right" approach — people are different, everyone has their own habits, established practices, and working styles, and I fully allow for, and have no doubt, that there are people who are used to dealing with a pile of different projects in one directory and a pile of different sessions in one picker, and they just find what they need via search.

But not everyone is like that. There's a large number of people accustomed to order, separation, and organization.

And, frankly, an approach that implies separation and organization is more deserving of being the default than a "free-for-all" and a "jumbled heap."

That said, neither approach should or can be mandatory or imposed, and neither of them should be the default for everyone. The default should be chosen and saved by the user.

—
Reply to this email directly, view it on GitHub<https://github.com/anthropics/claude-code/issues/46549#issuecomment-4238387781>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5GYU4WCY3XAVYZTVNQEHZT4VUQFZAVCNFSM6AAAAACXUXBDFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZYGM4DONZYGE>.
You are receiving this because you authored the thread.

Direct answer to the git log --all question: yes, scoped-by-default is the stronger single default.

1. Consistency with the rest of the dev toolchain. git log, git status, ls, rg, find, cargo — all default to current scope and widen with an explicit flag (--all, path arg). Wide-by-default --resume is the outlier, not the norm.

1. Asymmetric failure modes. Scoped default → "where's my session?" → user hits Ctrl+A, learns the filter exists, moves on. Wide default → user lands on the wrong project's session, silently does work in the wrong context, recovery cost is much higher.

1. Discoverability cuts both ways. The "can't find my session from another dir" complaint is solved by the hint line already at the bottom of the picker (Ctrl+A to only show current directory). If hint-line discoverability works for the narrow filter, it works equally for the wide one — and scoped default still has better default-case ergonomics.

@Agriv8's persisted-setting ask is still the ideal answer. But if only one default can ship, scoped wins on all three counts.

Revert pushed in. should be in the next release. sorry for the noise. will add another change for --all

Glad that this is reverted.

There may be a time cutoff issue also here where the current defualt /resume loads some limited X sessions and Ctrl + A does filtering on the fetched sessions. I am seeing empty results for projects that I haven't worked on for few weeks. Hopefully this will get resolved with the revert.

There may be a time cutoff issue also here where the current defualt /resume loads some limited X sessions and Ctrl + A does filtering on the fetched sessions. I am seeing empty results for projects that I haven't worked on for few weeks. Hopefully this will get resolved with the revert.

Yes I am still getting this even on v2.1.107. Really big and annoying issue.

Thank you for being sensible and changing it back. much relieved and impressed the time to respond.

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.