Skip to content

Move threads between local and remote environments #11

Open

Description

@lorenzkrinner

Continue an existing thread on another environment, including local-to-cloud and cloud-to-local moves. This combines the two original transfer requests.

Scope and acceptance:

  • Carry the conversation and relevant uncommitted project work to the destination.
  • Validate the destination provider, repository, permissions, and required configuration.
  • Show transfer progress, the destination, and a recoverable failure state.
  • Keep one runnable owner and avoid losing work if a transfer fails.
  • Support moving in both directions.

Review upstream work first:

The original request includes moving while an agent is working. Decide explicitly whether to wait for the turn boundary or stop/checkpoint/resume. Do not describe a fresh-session transcript handoff as preservation of the provider-native session. Terminal processes and native runtime state need separate support decisions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions