[BUG] claude remote-control subcommand hangs on commands; claude --remote-control flag ignores --name

Resolved 💬 2 comments Opened Apr 10, 2026 by dreamspy Closed Jun 20, 2026

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?

Description

Two related issues with Remote Control on v2.1.98:

  1. claude remote-control (subcommand) — commands hang

The subcommand starts fine and shows "Connected" with the capacity screen, but when connecting from Claude Desktop or claude.ai/code and sending a command, the client shows an
infinite spinner. No response is ever returned. Tested from both macOS (Claude Desktop) and iOS (Claude app) — same behavior on both. Tested running claude remote-control from Mac and ubuntu.

This was working previously some hours ago with no local configuration changes.

  1. claude --remote-control (flag) — ignores --name

The flag variant works correctly for executing commands, but the --name flag is ignored. Sessions auto-rename to "new coding session" and then to conversation-derived names, making it
impossible to set a persistent display name.

claude --remote-control --name "my-fixed-name"
# Session initially shows "my-fixed-name" but gets renamed after first message

--remote-control-session-name-prefix has the same behavior — only affects the initial name, then gets overwritten.

Expected behavior

  1. claude remote-control should relay commands to spawned sessions without hanging
  2. claude --remote-control --name "X" should keep "X" as the session name

Environment

  • Claude Code: 2.1.98
  • Server OS: Ubuntu 24.04 LTS (Linux 6.8.0-107-generic, x86_64)
  • Also tested on a Mac as a server.
  • Clients tested: Claude Desktop on macOS, Claude app on iOS
  • Sessions run inside tmux over SSH

Reproduction

# Issue 1: subcommand hangs
claude remote-control --name "test" --spawn=same-dir
# Connect from Claude Desktop or claude.ai/code → send any message → spinner forever

# Issue 2: flag ignores name
claude --remote-control --name "test"
# Connect and send a message → session name changes to "new coding session"

What Should Happen?

Expected behavior

  1. claude remote-control should relay commands to spawned sessions without hanging
  2. claude --remote-control --name "X" should keep "X" as the session name

Error Messages/Logs

don't have any

Steps to Reproduce

Reproduction

# Issue 1: subcommand hangs
claude remote-control --name "test" --spawn=same-dir
# Connect from Claude Desktop or claude.ai/code → send any message → spinner forever

# Issue 2: flag ignores name
claude --remote-control --name "test"
# Connect and send a message → session name changes to "new coding session"

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

it worked some hours ago in the same version

Claude Code Version

2.1.98

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗