🔶 Launch HN：Skillsync（YC W26）让 AI 聊天会话可在不同 Agent 间迁移

嗨，HN，我们是 Nars 和 Nishant，Skillsync 的联合创始人（

https://skillsync.com

）。

Skillsync 让你可以在所有编程 Agent 之间迁移 AI 聊天会话。我们的大部分工作都存在于对话中，而这些对话目前分散在各个 Agent 里。尽管它们存储在本地，但不同 Agent 使用不同的格式。这很麻烦，因为你无法在不从头开始的情况下简单地切换 Agent。随着时间推移，我们不断投入技能和记忆，也就被锁定在单一供应商及其 Agent 之中。Skillsync 充当一个通用转换器：它可以迁移整个会话，包括所有消息、推理过程和工具调用，让你能够从上次中断的地方继续。

Skillsync 将你的全部会话汇集到一个地方，并使其可搜索。它会拆解每个会话所携带的内容，包括 Agent 实际正在使用哪些已加载的技能，从而让过时上下文一目了然。你还可以创建共享工作区，在团队中同步会话，并构建自己的闭环系统。除非你将内容共享到工作区，否则一切都在本地运行。

其核心是一个名为 txcript 的开源 Rust 引擎（https://github.com/skillsynchq/txcript）。它能将一个 Agent 的磁盘会话格式转换为另一个 Agent 的格式，并映射对话、推理和工具历史。你可以把它理解为面向 Agent 会话的 ffmpeg 或 pandoc。

在这个引擎之上，是一款本地优先的桌面应用。你的 Agent 会话通常散落在不同工具的目录中，使用你根本不会手动阅读的格式；该应用将它们集中呈现在一个界面中，使对话、推理过程和工具调用真正变得可读。你可以回顾发生过什么，将一个会话迁移到另一个 Agent，或与队友共享它。

技能和记忆会以你拥有的、可移植且人类可读的 Markdown 格式存储，并通过 MCP 向任何 Agent 提供搜索和选择性检索能力。

会话及其转换都在你的机器本地运行。唯一会离开本机的内容，是你明确共享到团队工作区的信息。

让我们感到意外的是，很多人其实已经在不知不觉中被锁定了。只有当你尝试离开时，才会发现自己被困在某个 Agent 或开发框架中；而到那时，你可能已经积累了数月会话，它们被困在只有该工具才能读取的格式里。这种锁定在成本真正显现前几乎是不可见的。

一旦会话具备可移植性，它们就不再是一次性日志，而会成为你真正可以持续构建的资产：你可以发现自己的工作模式，把会话交接给其他人，让非技术背景的队友从工程师离开的地方继续。会话最终会成为协作的基本单元，但目前它们却正在被丢弃。

在 Skillsync 之前，Nars 和我曾构建过一个开源支付编排器，让商家能够在多个支付处理商之间路由，而不是被锁定在单一服务商中（GitHub 星标超过 3 万）。通过让不兼容的系统互操作来对抗供应商锁定，正是我们当时的核心工作。我们带着另一个想法进入 YC，但随着我们越来越多地在编程 Agent 中工作，我们从另一面看到了同样的问题：你的上下文被锁定在最初选择的 Agent 中，因为每个 Agent 以不同方式存储会话，而这些内容无法迁移。

我们看到用户正在通过 Skillsync 做的一些事情包括：

• 在任务进行到一半时，在 Claude Code、Codex 和 Cursor 之间迁移会话；例如，当某个服务达到使用额度上限时，可以切换到另一个服务继续工作。

• 在浏览器中的 Claude 聊天里思考问题，然后把整个对话线程交给 Claude Code 或 Codex 来实现。

• 与团队共享研究会话。每个人上传自己的会话，让队友及其 Agent 能在彼此的工作基础上继续推进，而不是重复劳动。

它目前提供 Mac 应用、CLI 和 MCP。以下是演示：视频/嵌入内容：Skillsync 演示。我们很希望听到大家的反馈，也乐于回答问题！

Hey HN, we're Nars & Nishant, founders of Skillsync (

https://skillsync.com

)

Skillsync lets you move your AI chats across every coding agent. Most of our work exists as conversations, which are currently scattered across our agents. Though stored locally, these conversations use different formats. This is annoying because you cannot simply switch between agents without starting over. We get locked into a single provider and their agent as we invest in skills and memories over time. Skillsync acts as a universal converter. It moves the entire session, including all the messages, reasoning and tool calls so you can pick up right where you left off.

Skillsync collects all your sessions in one place and makes them searchable. It breaks down what each session is carrying, including which loaded skills the agent is actually using, making stale context easy to spot. You can also create shared workspaces to sync sessions across your team. You can build your own closed loop systems. Everything runs locally except when you share to workspaces.

The core is an open-source Rust engine called txcript (https://github.com/skillsynchq/txcript). It translates a session from one agent's on-disk format into another's, mapping conversation, reasoning, and tool history. Think ffmpeg or pandoc, but for agent sessions.

On top of that engine is a local-first desktop app. Your agent sessions are normally scattered across different tools' folders in formats you'd never read by hand; the app surfaces them in one place with a UI that makes them actually readable, the conversation, the reasoning, and the tool calls, so you can revisit what happened, move a session into another agent, or share it with a teammate.

Skills and memory are stored as portable, human-readable markdown you own, and exposed to any agent over MCP for search and selective retrieval.

Sessions and translation run locally on your machine. The one thing that leaves is what you explicitly share into a team workspace.

It’s been surprising to us to see how locked-in people already are without realizing it. You don't notice you're trapped in one agent or harness until you try to leave, and by then you've got months of sessions stuck in a format only that tool can read. The lock-in is invisible right up until it's expensive.

Once sessions are portable, they stop being disposable logs and become something you can actually build on, spotting patterns in how you work, handing a session off to someone else, letting a non-technical teammate pick up where an engineer left off. The session turns out to be the unit of collaboration, and right now it's being thrown away.

Before Skillsync, Nars and I built an open-source payment orchestrator that let merchants route across many processors instead of getting locked into one (30k+ GitHub stars). Fighting vendor lock-in by making incompatible systems interoperate was the whole job. We came into YC with a different idea, but the more we lived inside coding agents the more we saw the same problem from the other side: your context is locked into whatever agent you start with, because every agent stores sessions differently and none of it moves.

Some of the things we’re seeing people do with Skillsync are:

- Moving a session between Claude Code, Codex, and Cursor mid-task, including when you hit a usage limit on one and want to keep going on another.

- Thinking through a problem in a browser Claude chat, then handing the whole thread to Claude Code or Codex to build.

- Sharing research sessions with a team. Everyone uploads their sessions, so teammates and their agents can build on each other's work instead of repeating it.

It's available as a Mac app, CLI and MCP. Here's the demo: https://youtu.be/7hVhSnSKGl8. Would love to hear your feedback and answer questions!