claude-code - 💡(How to fix) Fix Feature request: Maintain remote session through CLI upgrade [1 comments, 2 participants]

TL;DR

Implementing a mechanism to cache session metadata and automatically reattach sessions after a CLI upgrade is likely the most effective fix.

Guidance

• Investigate modifying the claude --resume command to store session metadata in a cache, allowing for automatic reconnection after an upgrade.
• Consider adding a new command, such as claude --reattach-all, to simplify the process of reestablishing sessions after an upgrade.
• Evaluate the feasibility of maintaining active remote sessions during the upgrade process, potentially by using a separate process or service to manage sessions.
• Assess the impact of delayed upgrades on overall system stability and security, and weigh this against the inconvenience of reattaching sessions.

Example

No code snippet is provided due to the lack of specific technical details in the issue.

Notes

The ideal solution would involve minimal changes to the existing CLI architecture, while still addressing the user's needs. However, the feasibility of each proposed solution depends on the underlying implementation of the Claude Code CLI and its remote session management.

Recommendation

Apply a workaround, such as implementing a script to automate the reattachment of sessions after an upgrade, until a more permanent solution can be developed. This approach allows users to mitigate the disruption caused by upgrades while a more robust fix is being implemented.