[FEATURE]

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 27, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Subject: Please let me move a session between cloud and local (and back)

It's genuinely infuriating that a Claude Code session is trapped on the surface it started on. I did a big chunk of work in a cloud session, and now that I need to finish it locally — because the cloud sandbox physically can't reach my droplet or my Mac to deploy — there is no "continue this session locally" button. My only option is to have Claude write a summary and paste it into a fresh local session, praying nothing important got left out.

That's backwards. The whole point of the cloud/local split is flexibility, but in practice I'm punished for using both: every handoff is a manual, lossy, copy-paste ritual that throws away the real conversation history, the reasoning, and the context the model actually built up. A summary is a lossy compression of a session that already exists — I shouldn't have to recreate state that's sitting right there.

Proposed Solution

What I want is simple: pick up the same session on the other surface. Cloud → local when I need to touch machines the sandbox can't reach; local → cloud when I want it to keep running while I'm away. Same transcript, same context, no re-briefing.

Short of full portability, even a "fork this session to local" that carried the transcript automatically would be a massive improvement over "have the model write you a note." Please prioritize this — it's the single biggest friction in an otherwise great workflow.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗