Launch HN: Skillsync (YC W26) – AI chat sessions made portable across agents

Launch HN: Skillsync (YC W26) – AI chat sessions made portable across agents

16 pointsby cat-whisperer62 comments

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • this is awesome! i’ve been working on a tool for cross-harness integration tests - https://dynobox.xyz - and one of the hardest parts has been writing adapters for each harness since their transcript formats are all so different.

    really excited to check out txcript… a shared translation layer could make my life sooo much easier!

  • This is awesome! You solve an immediate need of mine for:

    https://github.com/gitsense/chat/tree/readme-scale-knowledge

    Since I only support Pi natively, your solution will make it possible for codex/claude/etc. users to discover their conversations in my app. Will definitely include this as workaround for making codex, claude and other sessions available for discovery.

  • I was thinking about doing this. If we treat ChatGPT like your local llm server, you basically open up a browser session, intercept all traffic and stick a local OpenAI compatible rest server that mutilates your input upstream through the ChatGPT ui, and then intercepts downstream and pushes it out your server.

    API call to server

    Then

    Server leverages chrome plugin to send your llm call through the plugin , through the ui, wait for response , intercept, repackage and reroute it back out as a server response.

    Then that $20 sub stretches to all uses cases for a developer.

  • Love this. Easily the most annoying thing about modern Agent development across Claude, Codex, etc. One nit: You don't auto-discover "archived" chats from Codex. They have to be unarchived and the app restarted before being found.
  • The portability angle is interesting. We measured coding-agent sessions and found ~94.5% of the accumulated context was reused across turns.

    Two questions on the translation side: what gets dropped or normalized when a session crosses agents (reasoning blocks, tool-call IDs, provider-specific message types)? And is the output serialized deterministically, so the receiving agent's cache can warm up and stay warm after the move?

  • Hi team, I tried to email you with a privacy question. I used the email address on your Privacy page, but it bounced back as unknown, and there's no other contact address/form on your website. Is there a way to get in touch?
  • I have made simple macos app to export my claude sessions to markdown(plus ordinal jsonl) and i just continuously sync it to dropbox.

    i do the same for apple notes and imessage. so very portable

    https://apps.apple.com/us/app/exporter-notes-to-markdown/id6...

  • I went the opposite way, and I think it's worth mentioning the cost of that choice. My conversation doesn't carry over. Only what a session explicitly recorded does. This includes decisions, open questions, verified items, and what's left to do. Anything that wasn't recorded is gone, and that's a real loss, not just a small part of the process.

    I went with this approach because the transcript doesn't go into a file; it goes into another live session, which messes up its flow. We've already talked about this a bit when we were discussing "how to make reading Markdown cheaper." My answer was different: don't bring it over at all. The next session doesn't need to know how we got there—it just needs to know what we decided and what we've actually verified.

    I don't think we've talked about this in this thread yet. Portability is all about a session that's already wrapped up. I often have two sessions open at the same time. One is building an endpoint, and the other is the screen that calls it. They need to ask each other before both build on different assumptions. Moving the transcript around won't fix this. What's needed is a message, not a copy.

    I made a small open-source layer for this: a mailbox and a "walkie-talkie" for sessions in the clients you've already opened - https://github.com/automatis-tools/agents-can-communicate. It doesn't transfer memory and doesn't detect discrepancies on its own. The session has to check for those things.

Explore Birbla archives