Bug Report: Claude Desktop v1.1.7714 update broke Code sessions via Remote Control regression

Resolved 💬 2 comments Opened Mar 20, 2026 by SUSUTOGO Closed Mar 21, 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?

Claude Desktop v1.1.7714 introduced a regression that broke Claude Code sessions entirely.

Before v1.1.7714, Claude Desktop launched Claude Code directly without requiring a Remote Control channel. After v1.1.7714, the app changed architecture to communicate with Claude Code CLI via an IPC socket through a 'remote-control' mechanism. A LaunchAgent (com.claude.remote-control.plist) was created to automate this — but it consistently fails at login with LastExitStatus = 256 (exit code 1).

Impact:

  1. Claude Desktop Code sessions fail silently (exit code 1, no error shown to user)
  2. Remote Control LaunchAgent enters infinite restart loop due to KeepAlive=true
  3. Each restart attempt consumes usage quota — significant quota was consumed without any intentional use
  4. User has no visibility into what is happening in the background

What I have verified:

  • Claude Code binary works correctly in Terminal
  • Browser version (claude.ai/code) works correctly
  • Only Desktop App Code interface is broken
  • After manually running the two commands below, everything works
  • Problem reproduces on every reboot

Workaround required every reboot:

sudo launchctl limit maxfiles 65536 65536
claude remote-control

This should be handled automatically by the installer or LaunchDaemon.

What Should Happen?

The installer or LaunchDaemon should automatically set system-level maxfiles limits so that claude remote-control starts successfully at login without manual intervention.

Requested fixes:

  1. The installer should set system-level maxfiles automatically
  2. The LaunchAgent KeepAlive should not cause infinite retry loops on failure
  3. Users should not lose quota due to background failure loops
  4. If quota was consumed due to this background failure loop, please review

Error Messages/Logs

Error log (/tmp/claude-rc-err.log):
  error: An unknown error occurred (Unexpected)
  error: An unknown error occurred, possibly due to low max file descriptors
  Current limit: 256

LaunchAgent: com.claude.remote-control.plist
LastExitStatus = 256 (exit code 1)

Steps to Reproduce

Timeline:

  • Mar 19: Claude Desktop updated to v1.1.7714
  • Mar 20 16:44: Claude Code CLI updated to v2.1.78
  • Mar 20 23:44: com.claude.remote-control.plist LaunchAgent created
  • Mar 21: All Claude support files re-initialized after troubleshooting

Root Cause:
The system default maxfiles limit (256) is too low for claude remote-control to start. The LaunchAgent runs without sudo, so it cannot raise this limit itself.

Steps to reproduce:

  1. Install Claude Desktop v1.1.7714 on macOS Apple Silicon
  2. Install Claude Code CLI v2.1.78
  3. Reboot the system
  4. Try to start a Code session from the Desktop App
  5. Observe: session fails silently, LaunchAgent enters infinite restart loop

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Claude Desktop before v1.1.7714 (Mar 18 or earlier)

Claude Code Version

v2.1.78

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

System info:

  • macOS, Apple Silicon M2
  • Claude Desktop v1.1.7714
  • Claude Code CLI v2.1.78
  • Logs available on request

Related GitHub issues:

View original on GitHub ↗

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