[BUG] Repository not found when starting new chat on mobile app

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?

When a mobile session is remotely controlling a PC Claude Code session (shown as "연결됨 · 원격 제어" / "Connected · Remote control" on the session card), there is no visible or labeled way to disconnect it.

Issues found:

1. The session card itself has no "disconnect" action visible anywhere.
2. Long-pressing the card opens a menu with only two options: "이름 변경" (Rename) and "보관" (Archive) — neither is labeled as "disconnect."
3. "보관" (Archive) turns out to be the only action that actually ends the remote control connection, but this is not communicated anywhere in the UI. A user has no way to know that archiving = disconnecting without trial and error.
4. Because the connected session keeps running in the background on the phone, this drains phone battery, so users need a fast and obvious way to disconnect — which currently doesn't exist.

Additionally, the overall UX between the PC (Claude Code desktop/CLI) and the mobile app feels inconsistent — session management actions (connect/disconnect, rename, archive) use different terminology and different flows across platforms, making it hard for a user to build a consistent mental model of how sessions work.

Steps to reproduce:

1. Start a Claude Code session on PC
2. Connect to it remotely from the mobile app (shows "연결됨 · 원격 제어")
3. Try to find a way to disconnect from the mobile app — no explicit "disconnect" option is visible except by discovering that "보관" (Archive) does it

Expected: A clearly labeled "연결 해제" (Disconnect) action directly on the session card or in its menu, separate from Archive, with consistent terminology matching how sessions are described on PC. Overall assessment: Compared to competing tools (e.g. Codex), Claude Code's UI — including the remote control / session management flow described above — feels noticeably behind in terms of clarity and discoverability. Actions are hidden behind ambiguous menu items, error messages don't explain the cause, and terminology is inconsistent across platforms. This makes the product significantly harder for beginners to use without trial and error or external help.

What Should Happen?

There should be a clearly labeled "연결 해제" (Disconnect) action directly on the session card or its menu, separate from "보관" (Archive), so users can immediately understand and stop an active remote control connection without trial and error. Terminology and session-management UX should also be made consistent between the PC and mobile clients.

Error Messages/Logs

n/a

Steps to Reproduce

1. On a PC, start a Claude Code session
2. From the mobile app, remotely control that PC session (session card shows "연결됨 · 원격 제어" / "Connected · Remote control")
3. Try to find a way to disconnect the session from the mobile app
4. There is no visible "disconnect" button on the card. Long-pressing the card only shows "이름 변경" (Rename) and "보관" (Archive) — neither is labeled as disconnect
5. Tapping "보관" (Archive) turns out to be the only action that ends the remote connection, but this is undiscoverable without trial and error

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.233 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_