Skip to content

[FEATURE]:opencode-conversation-sync-skill #36509

Closed as not planned
Closed as not planned

Description

@TangGuoNiuBi

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

An OpenCode skill for backing up and restoring conversation history across devices.
https://github.com/TangGuoNiuBi/opencode-conversation-sync.git

Activity

  1. github-actions commented on Jul 12, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    If your request is distinct, please clarify what differentiates it from these existing issues.

  2. TangGuoNiuBi commented on Jul 12, 2026

    @TangGuoNiuBi
    Author

    This issue might be a duplicate of existing issues. Please check:

    If your request is distinct, please clarify what differentiates it from these existing issues.

    Unlike #27752 (vector DB for semantic search), #19017 (local save wish), and #9387 (single-session text export), this skill solves a distinct problem: cross-device conversation migration with full database fidelity. It provides bidirectional SQL export/import via git, with path-agnostic placeholder substitution, dry-run preview, and zero external dependencies. The existing issues focus on single-device persistence or human-readable export — none address moving complete conversation state between machines.

  3. TangGuoNiuBi commented on Jul 12, 2026

    @TangGuoNiuBi
    Author
    Image
  4. tranhailong commented on Jul 21, 2026

    @tranhailong

    sounds like it might be related to this one too #28340

    i'd like +1 the request please. would like to be able to continue the coding session that was started on my workstation while on the go with my mobile. so would be really useful to be able to retrieve the list of sessions from the server with the latest state.
    i think currently we're able to retrieve the state of a current coding session via direct url e.g. across device, but no way to get a list of session id, so it becomes a clunky copy paste the url somewhere so that you can re-retrieve it from another device

    https://<domain>/server/<some id>/session/<session id>

  5. tranhailong commented on Jul 21, 2026

    @tranhailong

    Actually I take that back. When I log in on a different device, the list of projects is not auto populated. But when I open a project with existing sessions, it will auto pull in the list of associated sessions.

    Can we make the list of opened project persist across devices please

  6. TangGuoNiuBi commented on Jul 21, 2026

    @TangGuoNiuBi
    Author

    感谢 @tranhailong 提供的背景信息!我认为我们的使用场景其实是不同的:

    你的场景:在移动设备上继续编码会话,这需要 opencode 服务端原生支持实时跨设备同步(项目列表 + 会话列表)。
    我的 skill:一个开发者侧的解决方案,用于通过 git 仓库托管对话数据,实现开发机之间完整的数据库级备份和迁移(例如工作台式机 ↔ 笔记本)。它依赖 git + Node.js,因此不适合移动设备使用。
    这两者是互补而非重叠的关系:

    服务端同步(你在请求的功能)需要在任何设备(包括手机)上实现轻量级、实时的访问——这需要内置到 opencode 本身。
    我的 skill 解决的是另一个问题:通过 git 仓库托管实现完整的对话数据可移植性,具有完整的数据库保真度(所有表、关系完整)、路径无关的占位符替换、dry-run 预览,以及零外部依赖。它是为那些希望通过 git 管理对话归档的开发者设计的,而不是为了在路上恢复会话。
    话虽如此,如果 opencode 最终发布了原生跨设备同步功能,我的 skill 仍然可以作为基于 git 的对话归档和版本管理工具——就像你既需要云同步也需要 git 仓库来管理重要数据一样。

    sounds like it might be related to this one too #28340

    i'd like +1 the request please. would like to be able to continue the coding session that was started on my workstation while on the go with my mobile. so would be really useful to be able to retrieve the list of sessions from the server with the latest state. i think currently we're able to retrieve the state of a current coding session via direct url e.g. across device, but no way to get a list of session id, so it becomes a clunky copy paste the url somewhere so that you can re-retrieve it from another device

    https://<domain>/server/<some id>/session/<session id>

  7. github-actions commented on Sep 21, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions