[BUG] remote-control --name is ignored: picker labels every server by git root, so servers in one repo are indistinguishable (refiling #86328)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

and mobile). The label is derived from the working directory — specifically from its git root, not from the directory itself, and not from --name.

Because the label comes from the git root, every server started anywhere inside one repository gets the same label. Servers started in <repo>/advisors/assistant and <repo>/advisors/finance both appear as <repo>. The only thing telling two entries apart in the picker is the capacity counter ("2 of 6 sessions" vs "3 of 4 sessions"), which a human cannot map back to a role.

This makes the documented multi-server workflow — one server per role, per purpose — unusable inside a monorepo. I run nine assistant personas, each with its own project directory, its own CLAUDE.md, its own skills and its own memory, all inside a single repository. In the picker they are all called <repo>.

There is no workaround short of splitting the repository or moving directories out of it — i.e. changing project layout to work around a label.

This was already reported in #86328 (filed 2026-08-13, labelled platform:windows) and closed by the stale bot on 2026-09-11 without a maintainer reply. It is not Windows-specific and still reproduces, so I am filing fresh as that closing comment suggests.

What Should Happen?

--name should set the label shown in the Remote Control picker, as the help text already promises:

--name <name> Name for the session (shown in claude.ai/code)


Failing that, the help text should state what the flag actually names, and some other mechanism should let users distinguish several servers running within one repository.

Error Messages/Logs

(none — the flag is accepted silently and has no effect)

Steps to Reproduce

1. Create a directory whose name differs from the name you will pass:

mkdir -p ~/scratch/rc-test-dir
cd ~/scratch/rc-test-dir

1. Start a Remote Control server with an explicit, distinct name:

claude remote-control --name rc-test-name --spawn same-dir --capacity 1

1. Read the TUI banner. It says rc-test-dir. Open the Remote Control picker on claude.ai/code or in the mobile app: the entry is also rc-test-dir.

The supplied name rc-test-name appears nowhere.

To see the git-root part of the bug:

1. In a git repository, start two servers in two different subdirectories, e.g. <repo>/sub-a and <repo>/sub-b:

cd <repo>/sub-a && claude remote-control --name alpha --spawn same-dir --capacity 4
cd <repo>/sub-b && claude remote-control --name beta  --spawn same-dir --capacity 6

1. Both entries in the picker are labelled <repo>. Neither alpha/beta nor sub-a/sub-b is shown; the two are distinguishable only by their capacity counters.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.277 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Xterm

Additional Information

• #86328 — same bug, closed as stale without triage
• #91826 — related, about server names in titles of spawned sessions
• #76206 — session name dropped by /remote-control (closed)