[FEATURE] Can't reach my nested repos from the claude agents @repo picker

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I keep my repos grouped in nested folders under a common parent. When I open claude agents from that parent the @repo picker shows almost nothing.

Two things put a dir in the picker. The first is repos directly inside the folder I launched from but only one level down. Mine sit deeper than that so I get nothing.

The other is the roster. That's any dir that's had a background session. It works but it's annoying because it clutters my view with completed sessions. Delete those and the @repo mentions disappear with them. The picker and the session list are the same thing. I can't have a repo in the picker without a session in my view.

Proposed Solution

I don't mind how. A few ideas:

• Look deeper than one level into nested folders.
• Or make the depth configurable.
• Or let me set the root folders to scan (a repoRoots list) so I launch once and see everything.
• Or reuse/refactor the roster so I can have permanent entries that don't show up as sessions. Just guessing on that one.
• Or whatever else fits best.

What I want is to open claude agents once and reach any repo with @. No symlinks and no clutter.

Alternative Solutions

I tried symlinking the nested repos to the top level just to see if it works. It does. The picker follows symlinks and even uses the link name. But I wouldn't want to live with it. I'd have to restart claude agents each time and the maintenance would be a pain. Add or delete a repo in my nested setup and I'd have to create or remove its symlink by hand.

The other route is the roster one above (a background session per repo). But like I said it clutters the view and deleting the sessions drops the repos again.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

1. I've got a bunch of repos in nested folders under a common parent.
2. I open claude agents once from that parent.
3. I type @ and want to pick any repo to dispatch a session into.
4. Most of them don't show because they're more than one level down and the picker doesn't look that deep.

Additional Context

This is the @repo picker in claude agents. The @ file mention in chat is a different thing.

I commented on #44947. It was already closed as stale.

I worked out the two-route behavior on v2.1.196.