[BUG] Remote control: timeout, resume failure, no context persistence, plan amendments lost

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

Four related issues with remote sessions in Claude Code (via Claude Desktop):

Bug 1: Remote sessions cannot resume after disconnect or archive

When a remote session disconnects or gets archived, attempting to resume it fails. The session state appears to be lost entirely, requiring a fresh session start.

Bug 2: 15-minute timeout without "enable remote control for all sessions"

If "enable remote control for all sessions" is NOT enabled in Claude Code settings, Claude Desktop (Code) times out after exactly 15 minutes. This is not documented and the timeout is not communicated to the user before it happens.

Bug 3: No memory or context persistence across remote control sessions

Remote sessions do not carry over conversation context or memory from prior sessions. When a session drops and a new one starts, all prior context is gone. This makes remote sessions significantly less useful for ongoing work.

Bug 4: Plan mode amendments not registered on rejection

When in plan mode, if the user rejects the plan (via ExitPlanMode) and provides amendment text explaining what to change, the amendment is not passed back to the agent. The agent receives only a generic rejection notice with no content, so it cannot act on the feedback. The user then has to repeat their amendment in a separate message.

Environment

• Claude Desktop: 1.1.9134 (87a63a), built 2026-03-26
• Claude Code CLI: 2.1.85
• macOS (Darwin 25.4.0)
• Date observed: 2026-03-27

What Should Happen?

Expected behavior

1. Remote sessions should be resumable after disconnect or archive
2. The 15-minute timeout should either not exist, be configurable, or be clearly documented/warned about
3. Memory and context should persist across remote sessions, or at minimum, a resumed session should automatically reload context from the prior session transcript
4. When a user rejects a plan and provides amendment text, that text should be forwarded to the agent so it can act on the feedback without the user repeating themselves

Error Messages/Logs

Steps to Reproduce

Steps to reproduce

Bug 1: Remote session resume failure

1. Start a Claude Code session via Claude Desktop (remote control)
2. Let the session disconnect (network drop, machine sleep) or get archived
3. Attempt to resume the session
4. Result: session fails to resume, requires starting fresh

Bug 2: 15-minute timeout

1. Open Claude Desktop with Claude Code integration
2. Ensure "enable remote control for all sessions" is NOT enabled
3. Start a remote session
4. Wait 15 minutes without interaction
5. Result: session times out silently with no warning

Bug 3: No context persistence

1. Start a remote control session, establish working context (discuss files, make plans)
2. Session disconnects or is archived
3. Start a new remote session
4. Result: no memory or context from the previous session is available

Bug 4: Plan amendments lost on rejection

1. Enter plan mode in Claude Code
2. Agent writes a plan and calls ExitPlanMode
3. Reject the plan and type amendment feedback in the rejection prompt
4. Result: agent receives generic rejection with no amendment text; user must repeat feedback

Possible workaround (Bug 3)

Start a new session that searches for all previous sessions, then pulls context from those transcripts to reconstruct the working state. This is manual and fragile but may partially address the context loss until a proper fix is in place.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.1.9134 and 2.1.85

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_