Remote Control session dies when idle - still not fixed in v2.1.85

Resolved 💬 3 comments Opened Mar 27, 2026 by gonzpereze Closed Mar 31, 2026

Description

Remote Control (/remote-control within an active session) stops responding after being idle for a short period. The session silently dies and becomes unresponsive from the phone/browser side.

Environment

  • Claude Code version: 2.1.85
  • Platform: Linux (Ubuntu)
  • Connection: via claude.ai/code on mobile

Steps to reproduce

  1. Start a Claude Code session normally
  2. Activate /remote-control within the session
  3. Connect from phone via claude.ai/code
  4. Leave idle for a short time (minutes)
  5. Try to send a message from the phone — no response

Expected behavior

The remote control session should remain responsive indefinitely (or at least for hours), similar to how a terminal session stays open.

What I've tried

  • CLAUDE_STREAM_IDLE_TIMEOUT_MS=600000 — no effect on server-side reaping
  • Running v2.1.85 which should include the fix from changelog: "Fixed several Remote Control issues: sessions silently dying when the server reaps an idle environment"

Notes

The changelog for v2.1.78 mentions this was fixed, but the issue persists. The server still appears to reap idle remote control environments, making the feature unusable for its primary use case (checking in from mobile when away from the computer).

View original on GitHub ↗

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