Repository navigation
[FEATURE]: Export & Import sessions as first-class features in Desktop App #32696
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Descripción: Currently, opencode export and opencode import work via CLI, but the Desktop App has no UI for these operations. This makes it impossible to transfer/continue sessions between computers without dropping to the terminal.
Request: Add Export Session and Import Session buttons/commands directly in the Desktop App's TUI, so users can:
Export a session to a JSON file via the UI
Import a session from a JSON file via the UI
Ideally, continue an imported session seamlessly
This would enable users to move their sessions between machines without needing terminal access.
Reacted by Rodrigo, JeTSpice, Dmytro Fylyppenko and Felix Schaefer
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Jun 17, 2026
This issue might be a duplicate of existing issues. Please check:
opencode session exportto markdown or json #9387: Feature request foropencode session exportfunctionality (related)If your request is specifically about adding UI buttons/commands to the Desktop App for export and import (which #19513 also covers), please consider adding your use case there instead of opening a new issue.
RichardMM commentedon Jul 13, 2026
I have read through those issues, this is not a duplicate
JeTSpice commentedon Aug 19, 2026
One use case: I'm working at home and then at work. I'd like to keep the session. A low-fruit version is to be able to copy-paste the chat transcript. As it is, the chat is not copyable on the Windows Desktop version. And the /share command opens a webpage which is also not conveniently copyable. I think transferring the actual db is not practical because openCode says its db has hard-coded filepaths in it.
ian commentedon Sep 2, 2026
Another use case - I start on a long research session, export it, attach it to linear ticket.
Later in a month or two, rather than digging through past sessions, I just import the exported JSON session and get going again.
Or someone else can pick that session up from me.
feat(desktop): add session export to folder
feat(desktop): add session export to folder
ssearles commentedon Oct 14, 2026
Filed a narrower instance of this: #55542.
The desktop app's
/exportis JSON-only, while the TUI offers Markdown viaformatSessionTranscriptin the TUI package. From a user's side that means reading a conversation, or pasting it anywhere, requires the TUI — or hand-converting several megabytes of JSON.The format implementation already exists in the repo, so this looks like parity rather than new work. Not adding detail here; #55542 has the specifics.
neriousy commentedon Oct 19, 2026
This is implemented in v2, since v2.0.0: the desktop app has
/exportto save a session as JSON and an Import Session action on projects to load a JSON session. Update the desktop app to v2 to use these actions without the terminal. If you still see this on v2, please open a new issue with the details.