Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [SYS-032] Ultrareview crash kills Remote Control session — cascading failure, no isolation [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49501•Fetched 2026-04-17 08:39:21
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
ThatDragonOverThereThatDragonOverThere
Participants
github-actions[bot]github-actions[bot]ThatDragonOverThereThatDragonOverThere
Timeline (top)
labeled ×4commented ×1cross-referenced ×1

When crashes mid-run (in this case due to server rate limiting), it takes down the active Remote Control session along with it. Two independent subsystems — a cloud code review skill and a mobile RC connection — should never share failure modes.

Root Cause

When crashes mid-run (in this case due to server rate limiting), it takes down the active Remote Control session along with it. Two independent subsystems — a cloud code review skill and a mobile RC connection — should never share failure modes.

RAW_BUFFERClick to expand / collapse

Summary

When crashes mid-run (in this case due to server rate limiting), it takes down the active Remote Control session along with it. Two independent subsystems — a cloud code review skill and a mobile RC connection — should never share failure modes.

Reproduction

  1. Connect Claude mobile app via Remote Control
  2. Run from the desktop CLI
  3. Ultrareview hits server rate limit mid-run and crashes
  4. Remote Control session disconnects simultaneously

What should happen

Ultrareview crashes → ultrareview session ends → RC stays connected. The user's mobile session should be completely unaffected by what happens in a spawned cloud skill.

Impact

User loses both the review output AND their mobile session in a single event. Must reconnect RC manually. In this case it was the second consecutive failed ultrareview of the day — both sessions consumed credits, neither delivered output, and the second one also killed the RC connection.

Context

This is the third distinct ultrareview bug filed on launch day (2026-04-16):

  • #49465: Credit consumed on failed launch
  • #49466: Not available over Remote Control
  • This issue: RC killed by ultrareview crash

The pattern suggests ultrareview's remote agent session shares connection/process state with the parent CLI session rather than running as a fully isolated subprocess.

Environment

  • Claude Code v2.1.111
  • Windows 10, Claude iOS mobile app via Remote Control
  • Ultrareview crash cause: 'Server is temporarily limiting requests (not your usage limit) · Rate limited'

extent analysis

TL;DR

Isolate the ultrareview subprocess from the parent CLI session to prevent shared failure modes.

Guidance

  • Investigate the current implementation of the ultrareview subprocess and identify how it shares connection/process state with the parent CLI session.
  • Consider using process isolation techniques, such as running the ultrareview subprocess in a separate process or container, to prevent crashes from affecting the parent session.
  • Review the error handling mechanism for the ultrareview subprocess to ensure it does not propagate errors to the parent session, causing the Remote Control session to disconnect.
  • Analyze the system architecture to determine if there are any other shared resources or dependencies that could be contributing to the shared failure mode.

Example

No code snippet is provided as the issue does not contain sufficient technical details to create a specific example.

Notes

The solution may require significant changes to the system architecture and implementation, and may involve trade-offs between isolation and resource sharing.

Recommendation

Apply a workaround by isolating the ultrareview subprocess from the parent CLI session, as this is likely to prevent the shared failure mode and allow the Remote Control session to remain connected even if the ultrareview subprocess crashes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#mixed precision#training loop#device allocation#model download#tokenizer error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING