Escape key does not interrupt Claude when deep in tool chain (Remote Control / SSH sessions)

[aks4kj]

Problem

When Claude Code is executing a long chain of tool calls (file edits, SCP, SSH commands), pressing Escape (even twice) does not interrupt the execution. The progress counter keeps spinning with no way to stop it.

Steps to reproduce

1. Start a Claude Code session via Remote Control (claude.ai)
2. Give Claude a task that involves multiple sequential tool calls (e.g. editing several large files + SCP to remote server + SSH commands)
3. While the tool chain is executing (counter spinning), press Escape or Escape twice
4. Nothing happens — Claude continues executing

Expected behavior

Escape should interrupt the current tool chain and return control to the user.

Actual behavior

Escape has no effect. The only way to stop execution is to kill the session entirely and resume, losing context of what was happening.

Environment

• Claude Code via Remote Control (claude.ai)
• macOS 15.7.4
• Session involved: large file edits + scp + SSH commands to remote server

Impact

User is forced to kill the session and resume, which is disruptive especially during long deployments.

[github-actions]

Found 3 possible duplicate issues:

1. VS Code extension: uninterruptible processing loop causes irrecoverable data loss #43156
2. [BUG] Remote control - Web interface freeze when denying action and sending follow-up message - no free-text input in approval dialog #45330
3. [BUG] Remote run stuck, no cancel option, no visible timeout #45440

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #43156.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.