claude-code - 💡(How to fix) Fix [BUG]Remote-control session unresumable on iOS app after cost limit expires [1 comments, 2 participants]

When a Claude Code /remote-control session hits a cost limit, and no terminal confirmation was issued to pause/wait, the session cannot be resumed from the iOS Claude app once the limit expires. The iOS app shows a flashing activity icon as if the session is alive and processing, but no response is ever returned. The session is frozen in a perpetual loading state with no timeout, error message, or recovery option presented to the user. This is misleading as the UI implies work is in progress when the session is in fact stuck. After the cost limit resets, the user should be able to resume the /remote-control session from the iOS Claude app, or receive a clear error/notification with a recovery path. Session appears alive — activity icon flashes continuously — but no response is ever returned. No terminal pause/wait prompt was ever presented, so the user had no opportunity to intervene before the session became stuck. There is no timeout, no error surfaced, and no way to recover from within the iOS app.

Error Messages/Logs

UI bug: iOS app displays flashing activity icon indefinitely instead of surfacing an error, timeout, or recovery option

TL;DR

The issue can be mitigated by implementing a timeout or error handling mechanism in the iOS Claude app to handle stuck sessions after a cost limit expires without terminal confirmation.

Guidance

• Investigate the Anthropic API documentation to see if there are any existing error codes or callbacks that can be used to detect when a session has become stuck due to a cost limit expiration.
• Consider adding a timeout mechanism in the iOS Claude app to detect when a session has been inactive for an extended period, and surface an error or recovery option to the user.
• Review the /remote-control session implementation to determine if there are any opportunities to improve error handling or add recovery paths when a cost limit is imposed.
• Verify that the issue is not specific to the Opus Claude model or the macOS operating system by testing with other models and platforms.

Example

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

Notes

The root cause of the issue appears to be related to the handling of cost limit expirations in the /remote-control session implementation, but further investigation is needed to determine the exact cause and implement a fix.

Recommendation

Apply a workaround by implementing a timeout or error handling mechanism in the iOS Claude app to handle stuck sessions, as the issue is likely related to the current implementation and not a version-specific bug that can be fixed by upgrading.