Session transfer

Move an editing session from one machine or folder to another — open files, cursors, unsaved buffers, agent draft/context, and (optionally) the project tree.

Not available on the web build.

What is included

A ZIP bundle typically contains:

• Open tabs, active file, cursor/selection, scroll positions
• Unsaved buffer text
• Project files (respecting .gitignore, but always including open/dirty files)
• Agent artifacts under .rope_notes/ (preferences, memory, permissions, plans, session data, …)

You can also copy a JSON-only session summary (lightweight; does not carry full project files or unsaved buffers).

Export (manual)

1. Open the project.
2. File → Export Session…
3. Review the summary (open files, unsaved count).
4. Save Bundle to File… for a .zip, or Copy JSON for the snapshot only.
5. Copy the file to the other machine (USB, cloud drive, rsync, …).

Import (manual)

1. Open Rope Notes and the destination project folder.
2. File → Import Session…
3. Load Bundle from File… (or paste JSON).
4. Apply Session.
5. Resolve any overwrite vs keep conflicts for differing files.

After import (especially on Android), language analysis may restart so it picks up an updated package configuration.

Network transfer

The same bundle can stream over a paired connection (Iroh), reusing sync pairing / trusted peers. Use the network options in the session transfer dialog when both devices are online and discoverable or already trusted.

Tips

• Prefer ZIP when you need unsaved buffers and project files.
• Use JSON-only when you only need tab/cursor state and the project already exists on the destination.
• Large repos produce large ZIPs — ignore build artifacts via .gitignore.
• Paths are stored relative to the project root so the folder can live elsewhere on the destination.

Troubleshooting