Tencent open-sources MemHub: carry memory between AI tools

On October 16, 2026, Tencent released Hy-Memory 2.0, opening its memory model, developer SDK and the MemHub application built on them. An SDK is a toolkit that programs can call; MemHub is for users who want to connect history from different AI tools. Official announcement

MemHub brings explicitly authorized conversation and coding records into local memory for supported tools to read. It remains in preview. Platform availability depends on the downloadable assets for each release; the current documentation does not support Windows. MemHub project documentation

Suppose you switch between two coding assistants and repeatedly explain: “This project stores monetary amounts in cents and converts them to yuan only for display.” If the other assistant retrieves that convention as relevant memory, you have one less explanation to give from scratch.

First save the sentence as a test record without private information. After connecting the tools, use it to check whether the second tool preserves the distinction between storage and display. Finding relevant memory for the current question is called retrieval. This article covers installation and preparation of the example; each tool's connection steps still require guidance for the relevant version. This is a suggested verification scenario, and a claim that the tool has remembered something does not establish that it will use it correctly every time.

1. Choose the installation route. This example uses macOS, which requires version 13 or later. Open the official Releases page, choose the DMG package for your Mac's chip architecture, and check that release's release-manifest.json, the list of official installation files. If the relevant file is missing, do not treat source code or another platform's file as the installer.

2. Install and launch the application. Follow the release instructions to place MemHub in /Applications and launch it there for the first time. The documentation says the first launch installs background components. Closing the window closes the interface, while background components may continue running. Command-line users can inspect the state with memhub status and diagnose problems with memhub doctor, then follow the release instructions. Seeing the window is not proof that every tool connection is complete. Installation and runtime instructions · Status and diagnostic commands

3. Prepare an input and an expected answer you can compare. Use “Store amounts in cents; convert them to yuan for display” as the test record, and ask: “How are amounts stored and displayed?” The expected answer must retain both units and their corresponding uses. Note the tool providing the record and the tool that will read the memory, and confirm the separate permissions for source reading, model processing and tool reading.

4. Verify after connection. Public material does not fully list the import, authorization and connection buttons for every tool, so the preparation above is not presented as a completed cross-tool connection. After following the relevant version's connection instructions, compare the answer with the original sentence. If you cannot establish that the sentence entered memory or that the target tool has read access, pause here rather than expanding the import.

Local storage does not mean fully offline operation. When a third-party model is selected, authorized content needed for the task is sent to that provider. Check the provider and scope before enabling it. Uninstalling also retains memory data by default. Data and permission policy