claude-code - 💡(How to fix) Fix Native support for continuing a session across machines

TL;DR

To enable seamless session continuation across different machines, consider implementing an account-bound sync feature for session transcripts, memory, and plans.

Guidance

• Investigate replacing or supplementing the project-hash scheme with a project identifier resolved from the git remote origin URL to re-associate sessions across differing local paths.
• Explore using existing auth and account identity in the CLI to facilitate account-bound sync.
• Design a simple upload and download mechanism, such as claude session push and claude --resume --from-cloud, to synchronize session state across machines.
• Consider the implications of storing session data in the cloud, including security and data consistency.

Example

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

Notes

The proposed solution relies on the existence of auth and account identity in the CLI, as well as the ability to resolve a project identifier from the git remote origin URL. Additional considerations, such as data encryption and access controls, may be necessary when implementing account-bound sync.

Recommendation

Apply a workaround, such as manually zipping and transferring session files, until a more robust account-bound sync feature can be implemented. This is because the current workaround, although clunky, provides a functional solution for session continuation across machines.