Repository navigation
Feature Request: Portable Agent Workspaces — Export and Import Complete Sessions Across Machines #4028
bakwan79
started this conversation in
Feature requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Feature Request: Portable Agent Workspaces — Export and Import Complete Sessions Across Machines
Context
I regularly work with Prime Agent on multiple computers and would like to be able to move an ongoing session from one machine to another, in a way similar to what OpenCode offers.
However, simply exporting and importing a session file does not seem sufficient.
Prime Agent maintains and updates a significant amount of state outside individual session files. This global state can be essential to reproducing the same working environment when resuming a session on another machine.
The problem
A session is not entirely self-contained. Resuming it on another computer may require restoring several additional components:
Without these components, importing a session may restore the conversation but not the actual working environment in which it was created.
Proposed solution: Portable Agent Workspace / Session Bundle
I would like to propose a native export/import mechanism that packages a session together with all the state required to resume it elsewhere.
For example:
Possible CLI interface:
Important considerations
Ideally, the export mechanism would:
Alternative: Portable workspace synchronization
A complete archive might not be the only solution.
Another possibility would be to introduce a first-class portable workspace directory, containing both global agent state and session data, which could be synchronized between machines using Syncthing, rsync or other tools.
The important point is that Prime Agent should provide a documented and reliable way to identify and move all the state required to reproduce an agent's working environment.
Related discussions
/cdcommand to change an active session working directory #681 — Add/cdcommand to change an active session working directory.defaultSessionConfig.cwdinto a create whosecwdwas deliberately stripped #1124 — Resumed sessions run in the daemon's launch directory.Questions
I believe this would be particularly useful for developers working across multiple computers, remote development environments, and users who want reliable backups of their complete AI-assisted development sessions.
All reactions