hy-memory 2.0.1__tar.gz → 2.0.2__tar.gz

hy_memory-2.0.2/LICENSE

@@ -0,0 +1,61 @@
+Tencent is pleased to support the community by making Hy-Memory available.
+
+Copyright (C) 2026 Tencent. All rights reserved.
+
+Hy-Memory is licensed under Apache-2.0. Hy-Memory does not impose any additional restrictions beyond those specified in the license.
+
+For the avoidance of doubt, Hy-Memory refers solely to code, parameters, and weights made publicly available by Tencent in accordance with Apache-2.0.
+
+Terms of the Apache-2.0 License:
+--------------------------------------------------------------------
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+You must give any other recipients of the Work or Derivative Works a copy of this License; and
+You must cause any modified files to carry prominent notices stating that You changed the files; and
+You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
+If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
+You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

hy_memory-2.0.2/PKG-INFO

@@ -0,0 +1,310 @@
+Metadata-Version: 2.4
+Name: hy-memory
+Version: 2.0.2
+Summary: HY Memory - Industrial-grade dual-system cognitive memory framework
+Author: alvinfei
+License-Expression: Apache-2.0
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pydantic
+Requires-Dist: numpy
+Requires-Dist: openai<3,>=1.40
+Requires-Dist: python-dotenv
+Requires-Dist: pyyaml
+Requires-Dist: chromadb>=1.5.9
+Requires-Dist: kuzu
+Requires-Dist: langdetect
+Requires-Dist: scikit-learn
+Requires-Dist: tiktoken
+Requires-Dist: json-repair
+Requires-Dist: rank-bm25
+Requires-Dist: jieba
+Provides-Extra: qdrant
+Requires-Dist: qdrant-client; extra == "qdrant"
+Requires-Dist: fastembed; extra == "qdrant"
+Provides-Extra: faiss
+Requires-Dist: faiss-cpu; extra == "faiss"
+Provides-Extra: graph
+Requires-Dist: neo4j; extra == "graph"
+Provides-Extra: mysql
+Requires-Dist: aiomysql; extra == "mysql"
+Provides-Extra: rerank
+Requires-Dist: torch; extra == "rerank"
+Requires-Dist: transformers; extra == "rerank"
+Provides-Extra: all
+Requires-Dist: chromadb>=1.5.9; extra == "all"
+Requires-Dist: qdrant-client; extra == "all"
+Requires-Dist: fastembed; extra == "all"
+Requires-Dist: faiss-cpu; extra == "all"
+Requires-Dist: kuzu; extra == "all"
+Requires-Dist: neo4j; extra == "all"
+Requires-Dist: aiomysql; extra == "all"
+Requires-Dist: torch; extra == "all"
+Requires-Dist: transformers; extra == "all"
+Provides-Extra: dev
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: pytest-asyncio; extra == "dev"
+Requires-Dist: httpx; extra == "dev"
+Requires-Dist: ruff; extra == "dev"
+Dynamic: license-file
+
+<p align="center">
+  <img src="docs/images/hunyuanlogo.png" alt="Tencent Hunyuan" width="260">
+</p>
+
+<h1 align="center">Hy Memory</h1>
+
+<p align="center">Production-grade dual-system cognitive memory for LLM agents.</p>
+
+<p align="center">
+  <a href="#latest-news"><img src="https://img.shields.io/badge/news-latest-e65100?style=flat-square" alt="Latest News"></a>
+  <a href="#papers"><img src="https://img.shields.io/badge/papers-research-68448b?style=flat-square" alt="Papers"></a>
+  <a href="#quick-start"><img src="https://img.shields.io/badge/get_started-quickstart-149954?style=flat-square" alt="Get Started"></a>
+  <a href="#system-architecture"><img src="https://img.shields.io/badge/architecture-overview-007ec6?style=flat-square" alt="System Architecture"></a>
+  <a href="#support"><img src="https://img.shields.io/badge/support-docs-00897b?style=flat-square" alt="Support"></a>
+  <a href="https://huggingface.co/tencent/Hy-Memory-30B-A3B"><img src="https://img.shields.io/badge/model-Hugging%20Face-ffd21e?style=flat-square" alt="Hugging Face Model"></a>
+  <a href="memhub/README.md"><img src="https://img.shields.io/badge/MemHub-README-f28c45?style=flat-square" alt="MemHub"></a>
+  <a href="https://memory.hunyuan.tencent.com/"><img src="https://img.shields.io/badge/website-Hy%20Memory-0052d9?style=flat-square" alt="Website"></a>
+  <a href="https://discord.gg/x56wEb2PX"><img src="https://img.shields.io/badge/Discord-memory%20channel-5865f2?style=flat-square&logo=discord&logoColor=white" alt="Discord"></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-4c6ef5?style=flat-square" alt="Apache-2.0 License"></a>
+</p>
+
+English | [中文](README.zh.md)
+
+**[Hy Memory](https://memory.hunyuan.tencent.com/)** ([Official Website](https://memory.hunyuan.tencent.com/)) is a production-grade dual-system cognitive memory engine and Python SDK (`hy-memory`) for self-evolving LLM agents, providing specialized memory pipelines across three task scenes: hierarchical long-term cognitive memory for **Chat**, two-layer fact and reusable-experience memory for **Working**, and version-evolution diff-chain tracking for **Coding**. Built on top of Hy Memory, **[MemHub](memhub/README.md)** is a local-first desktop and CLI product that unifies conversation history and coding traces from user-authorized AI applications (such as Claude Code, Cursor, Codex, OpenCode, and Qwen Code) into a single managed runtime and local data directory, enabling governed cross-application memory recall.
+
+<div align="center">
+  <video src="https://github.com/user-attachments/assets/94405890-8429-47c2-9084-38f7ed9f126f" controls width="640"></video>
+  <p><b>MemHub Demo Video</b></p>
+</div>
+
+---
+
+## Latest News
+
+* *<mark>[new]</mark>* 🔥🔥🔥 **[2026-10]**: 🚀 **Released** **Hy Memory 2.0 (`hy-memory==2.0.1`)** on [PyPI](https://pypi.org/project/hy-memory/2.0.1/) and open-sourced the **Hy-Memory** monorepo together with **[MemHub](memhub/README.md)**!
+* *<mark>[new]</mark>* 🔥🔥🔥 **[2026-10]**: 🚀 **Open-sourced** **[Hy-Memory-30B-A3B](https://huggingface.co/tencent/Hy-Memory-30B-A3B)** on Hugging Face along with its [technical report](https://arxiv.org/abs/2610.22196) on attributed reinforcement learning for long-term memory writing!
+* *<mark>[new]</mark>* 🔥🔥 **[2026-09]**: 📊 **Released** **[CMB: A Coding Memory Benchmark for Long-Horizon and Interleaved Coding Agents](docs/papers/CMB_A_Coding_Memory_Benchmark_for_Long_Horizon_and_Interleaved_Coding_Agents.pdf)** (submitted to **ICLR 2027**).
+* *<mark>[new]</mark>* 🔥🔥 **[2026-08]**: 🎉 **Accepted** at **EMNLP 2026**: **[Memory Beyond Recall: A Dual-Process Cognitive Memory System for Self-Evolving LLM Agents](https://arxiv.org/abs/2606.09483)**!
+* 🔥 **[2026-05]**: 🌟 **Initial Release** Released **[Hy Memory 1.0](https://mp.weixin.qq.com/s/dH5PGpxqArFZkSq3-QxWYA)**, our first-generation dual-system cognitive memory framework for self-evolving LLM agents.
+
+---
+
+## Papers
+
+Welcome to the **Hy Memory Research Family**, covering cognitive chat memory, long-horizon coding memory, and RL-trained memory writing models:
+
+> [**Memory Beyond Recall: A Dual-Process Cognitive Memory System for Self-Evolving LLM Agents**](https://arxiv.org/abs/2606.09483) *(Accepted at **EMNLP 2026**)*  
+> **TL;DR:** Proposes the dual-process (System 1 + System 2) cognitive memory architecture for **Chat**, organizing personal memory into an 8-layer hierarchy (raw dialogues, atomic facts, summaries, schemas, and prospective intentions) with conflict reconciliation and cross-domain schema induction.  
+> 📄 Paper: https://arxiv.org/abs/2606.09483
+
+> [**CMB: A Coding Memory Benchmark for Long-Horizon and Interleaved Coding Agents**](docs/papers/CMB_A_Coding_Memory_Benchmark_for_Long_Horizon_and_Interleaved_Coding_Agents.pdf) *(Submitted to **ICLR 2027**)*  
+> **TL;DR:** Introduces a benchmark and two-layer + version-evolution diff-chain memory method for long-horizon **Coding** agents, preserving both reusable engineering experiences and exact code revision trajectories across interleaved tasks.  
+> 📄 Paper: [docs/papers/CMB_A_Coding_Memory_Benchmark_for_Long_Horizon_and_Interleaved_Coding_Agents.pdf](docs/papers/CMB_A_Coding_Memory_Benchmark_for_Long_Horizon_and_Interleaved_Coding_Agents.pdf)
+
+> [**Hy-Memory-30B-A3B: Attributed Reinforcement Learning for Long-Term Memory Writing**](https://arxiv.org/abs/2610.22196) *(Open Model Technical Report)*  
+> **TL;DR:** Trains a 30B-A3B MoE model via attributed reinforcement learning specifically for high-precision long-term memory extraction and conflict reconciliation.  
+> 📄 Paper: https://arxiv.org/abs/2610.22196 · Model: https://huggingface.co/tencent/Hy-Memory-30B-A3B
+
+---
+
+## Quick Start
+
+### 1. Installation
+
+```bash
+pip install hy-memory==2.0.1              # core (includes ChromaDB and Kuzu)
+pip install "hy-memory[qdrant]==2.0.1"    # + Qdrant
+pip install "hy-memory[faiss]==2.0.1"     # + FAISS
+pip install "hy-memory[graph]==2.0.1"     # + Neo4j
+pip install "hy-memory[mysql]==2.0.1"     # + MySQL cache
+pip install "hy-memory[rerank]==2.0.1"    # + local multilingual cross-encoder rerank
+pip install "hy-memory[all]==2.0.1"       # everything
+```
+
+### 2. Configuration
+
+Only an LLM and an embedding endpoint are needed; any OpenAI-compatible service works:
+
+```bash
+export MEMORY_LLM_API_KEY="sk-your-key"
+export MEMORY_LLM_BASE_URL="https://api.deepseek.com"
+export MEMORY_LLM_MODEL="deepseek-chat"
+
+export MEMORY_EMBEDDER_API_KEY="sk-your-key"
+export MEMORY_EMBEDDER_BASE_URL="https://dashscope.aliyuncs.com/compatible-mode/v1"
+export MEMORY_EMBEDDER_MODEL="text-embedding-v3"
+export MEMORY_EMBEDDING_DIMS=1024
+```
+
+Or use the OpenAI defaults with a single key:
+
+```bash
+export OPENAI_API_KEY="sk-your-key"
+```
+
+See the [Environment Variable Reference](docs/env_reference.md) for the full list.
+
+### 3. Chat Memory
+
+```python
+from hy_memory import HyMemoryClient
+
+client = HyMemoryClient(mode="pro")
+
+# Write: plain text or OpenAI-format messages
+client.add("I love sci-fi movies, especially Interstellar", user_id="user_1")
+client.add([
+    {"role": "user", "content": "Recommend a movie"},
+    {"role": "assistant", "content": "Try Interstellar — a sci-fi masterpiece by Nolan"},
+], user_id="user_1")
+
+# Search: returns the profile / normal / proactive channels
+results = client.search("What movies does the user like?", user_ids=["user_1"], limit=10)
+for mem in results["memories"]["normal"]:
+    print(f"  [{mem['score']:.2f}] {mem['content']}")
+
+client.close()
+```
+
+### 4. Working & Coding Memory
+
+Writes must include a tool-call trace (`tool_calls` or `role="tool"` messages) and take effect in `pro` / `ultra` mode only (`lite` ignores `scene` and stores everything as raw memory):
+
+```python
+messages = [
+    {"role": "user", "content": "Fix the timeout in the search client."},
+    {"role": "assistant", "content": "", "tool_calls": [{
+        "id": "call_1", "type": "function",
+        "function": {"name": "apply_patch", "arguments": '{"path":"src/search.py"}'},
+    }]},
+    {"role": "tool", "tool_call_id": "call_1", "name": "apply_patch",
+     "content": "Patch applied successfully"},
+]
+
+client.add(
+    messages,
+    scene="coding",                              # or "working"
+    user_id="user_123",
+    workspace_id="github.com/example/service",   # optional: isolate by repository / project
+    branch="fix/search-timeout",                 # optional: requires workspace_id
+)
+
+result = client.search(
+    "Which timeout implementation was finally kept?",
+    scene="coding",
+    user_ids=["user_123"],
+    workspace_id="github.com/example/service",
+    branch="fix/search-timeout",
+    limit=5,
+)
+
+result["facts"]          # fact layer
+result["experiences"]    # experience layer
+result["chain_block"]    # coding only: version-evolution context
+```
+
+### 5. Routing, Source Isolation & Advanced APIs
+
+- **Automatic scene routing**: When `scene` is omitted, writes without tool calls go straight to `chat` (zero LLM calls), and writes with tool calls are classified once into `chat` / `working` / `coding`. For searches, `search_mode="default"` goes to `chat` with zero LLM calls, while `search_mode="agentic"` performs scene classification, query rewriting, and time-range parsing. See [Working/Coding Scenes](docs/scene_coding_usage.md).
+- **Separate memories by source**: Pass `source="openclaw" | "cursor" | "codex"` on `add()` and filter with `include_sources` / `exclude_sources` on `search()` to isolate caller applications independently of `agent_id`.
+- **CRUD & System 2 evolution**: `client.get(id)`, `client.update(id, text)`, `client.delete(id)`, `client.list_memories(user_id=...)`, and `client.evolve(user_id=...)` (triggers System 2 in `ultra` mode).
+- **Per-call embedding endpoint override**: Pass `embed_override={"base_url": ..., "api_key": ...}` to `add()` / `search()` or use `with embed_endpoint_override(...):` for concurrency-safe endpoint switching.
+
+For provider configuration, storage backends, scenes, and the complete API, see the [Usage Guide](docs/usage.md).
+
+---
+
+## System Architecture
+
+<div align="center">
+  <img src="docs/images/architecture.svg" alt="Hy Memory architecture" width="95%">
+</div>
+
+Hy Memory provides three memory scenes (`scene`), one per kind of task. `add()` / `search()` go through the scene router first, then into the Chat or the Working / Coding pipeline (orange parts in the diagram are coding-only; without them the pipeline is Working):
+
+| `scene` | Tasks | Memory shape |
+|---|---|---|
+| `chat` | Small talk, personal information, preferences, general Q&A | Hierarchical memory (L0–L7) |
+| `working` | Productivity work: documents, spreadsheets, research, financial analysis, content creation, computer operation | Two-layer memory: session facts + reusable experiences |
+| `coding` | Software engineering: coding, debugging, testing, builds, APIs/SDKs, scripts, SQL | The same two-layer memory as `working`, plus a code version-evolution chain (diff chain) |
+
+### 1. Chat: Memory Hierarchy
+
+For long-term personal memory. Raw conversations are abstracted layer by layer into facts, summaries, a profile, and higher-level cognitive structures:
+
+| Layer | Name | Content |
+|---|---|---|
+| L0 | `BASIC_INFO` | Basic information |
+| L1 | `RAW` | Raw conversation (append-only) |
+| L2 | `FACT` | Atomic facts (versioned, immutable records) |
+| L3 | `SUMMARY` | Session summaries |
+| L4 | `IDENTITY` | Reserved |
+| L5 | `KNOWLEDGE` | Reserved |
+| L6 | `SCHEMA` | Mental models (abstract narrative templates, graph layer) |
+| L7 | `INTENTION` | Prospective intentions (with an expiry; demoted to ordinary facts once expired) |
+
+**Modes**
+
+| Mode | What it does | Graph DB | Use case |
+|------|--------------|----------|----------|
+| `lite` | Raw-only embedding writes and searches, no LLM calls; `scene` and `layers` are ignored | No | Vanilla vector RAG, fast ingestion, zero LLM cost |
+| `pro` | + LLM extraction + reconcile | Optional (`MEMORY_ENABLE_GRAPH`, off by default) | Standard workloads |
+| `ultra` | + System 2 schema induction + cross-domain sweeper (triggered by `evolve()`) | Yes (always on) | Full cognitive architecture |
+
+### 2. Working: Two-Layer Productivity Memory
+
+For getting things done. One session with tool calls (a trace) produces both layers at once:
+
+| Layer | What it records | Per session | Structure |
+|---|---|---|---|
+| **Facts** (`WorkingFact`) | What this session did: the task, the approach, the result | Exactly 1, no threshold | `statement`, `subject`, `files`, `details` (verbatim source) |
+| **Experiences** | Approaches that can be reused next time a similar task comes up | 0–N, must pass a value threshold | `task`, `search_keys`, `solution`, `boundary_envs`, `confidence` |
+
+The fact layer guarantees that work which was done is remembered; the experience layer makes what was learned reusable. The two layers link to each other (`fact.derived_experience_ids` ↔ `experience.source_fact_ids`), and superseded facts stay traceable through a task-progress chain (`fact_chain_summary`).
+
+### 3. Coding: Two-Layer Memory + Version-Evolution Chain
+
+Coding **reuses the same two-layer pipeline and data schema** as Working. It differs in three ways:
+
+| | Working | Coding |
+|---|---|---|
+| **Extraction spec** | Productivity-task spec | Software-engineering spec: the subject must be code or a decision; record exact coordinates (file / function / branch) instead of pasting code |
+| **Storage** | `coding_memory.db` + `*_coding_keys` / `*_working_facts` collections | `coding_memory_cv.db` + `*_cv` collections, fully isolated from working |
+| **Version-evolution chain** | None | **Yes**: how many times the same code was changed, and what each change was |
+
+**Why a version-evolution chain**: fact extraction deliberately avoids pasting code (the budget goes to more informative coordinates), so a version that was later reverted never appears in a fact.
+That version is usually not in the working tree or at HEAD either, so it cannot be read back afterwards. The chain stores the real diff of every version with zero LLM calls, filling in exactly the information a summary inevitably drops.
+
+**Design highlights** (`hy_memory/coding/chain_store.py`):
+
+- **A decorator, not a retriever**: the vector layer decides which facts are returned; the chain only attaches, under each fact, every revision of the code it touches (the user's words for that revision + the real diff).
+- **Change sources**: local Git diffs (set `MEMORY_CODING_CHAIN_REPO_ROOT`), or deterministic replace actions with `path` / `old` / `new` in the tool trace.
+- **Chain granularity & isolation**: one thread corresponds to one block of one function in one file on one branch, isolated by `user_id` + `workspace_id`.
+
+---
+
+## Support
+
+### Storage Backends
+
+- Vector stores: ChromaDB (default), Qdrant, FAISS
+- Graph stores (ultra mode): Kuzu (default), Neo4j
+- Working / Coding metadata: local SQLite
+
+### Documentation
+
+- [Usage guide](docs/usage.md) — full configuration reference, API details, deployment modes
+- [Environment variables](docs/env_reference.md) — settings and defaults
+- [Search and Reader guide](docs/hy_memory_search_skill.md) — reader selection, schema quotas, rerank, and return channels
+- [Working/Coding Scenes](docs/scene_coding_usage.md) — productivity-memory routing, response shapes, and coding chain behavior
+- [Graph memory design](docs/pro_graph_design.md) — graph projection, rerank, relation paths, and deployment limits
+- [Environment template](.env.example) — a copy-ready configuration template
+- [MemHub README](memhub/README.md) — local-first desktop & CLI product overview, runtime commands, and privacy boundaries
+- [OpenClaw plugin](plugins/openclaw/README.md) — agent integrations live under `plugins/` (overview: [plugins/README.md](plugins/README.md))
+
+### License
+
+Hy-Memory is licensed under Apache-2.0. See [LICENSE](LICENSE); third-party
+components remain subject to their respective licenses and notices.

hy_memory-2.0.2/README.md

@@ -0,0 +1,259 @@
+<p align="center">
+  <img src="docs/images/hunyuanlogo.png" alt="Tencent Hunyuan" width="260">
+</p>
+
+<h1 align="center">Hy Memory</h1>
+
+<p align="center">Production-grade dual-system cognitive memory for LLM agents.</p>
+
+<p align="center">
+  <a href="#latest-news"><img src="https://img.shields.io/badge/news-latest-e65100?style=flat-square" alt="Latest News"></a>
+  <a href="#papers"><img src="https://img.shields.io/badge/papers-research-68448b?style=flat-square" alt="Papers"></a>
+  <a href="#quick-start"><img src="https://img.shields.io/badge/get_started-quickstart-149954?style=flat-square" alt="Get Started"></a>
+  <a href="#system-architecture"><img src="https://img.shields.io/badge/architecture-overview-007ec6?style=flat-square" alt="System Architecture"></a>
+  <a href="#support"><img src="https://img.shields.io/badge/support-docs-00897b?style=flat-square" alt="Support"></a>
+  <a href="https://huggingface.co/tencent/Hy-Memory-30B-A3B"><img src="https://img.shields.io/badge/model-Hugging%20Face-ffd21e?style=flat-square" alt="Hugging Face Model"></a>
+  <a href="memhub/README.md"><img src="https://img.shields.io/badge/MemHub-README-f28c45?style=flat-square" alt="MemHub"></a>
+  <a href="https://memory.hunyuan.tencent.com/"><img src="https://img.shields.io/badge/website-Hy%20Memory-0052d9?style=flat-square" alt="Website"></a>
+  <a href="https://discord.gg/x56wEb2PX"><img src="https://img.shields.io/badge/Discord-memory%20channel-5865f2?style=flat-square&logo=discord&logoColor=white" alt="Discord"></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-4c6ef5?style=flat-square" alt="Apache-2.0 License"></a>
+</p>
+
+English | [中文](README.zh.md)
+
+**[Hy Memory](https://memory.hunyuan.tencent.com/)** ([Official Website](https://memory.hunyuan.tencent.com/)) is a production-grade dual-system cognitive memory engine and Python SDK (`hy-memory`) for self-evolving LLM agents, providing specialized memory pipelines across three task scenes: hierarchical long-term cognitive memory for **Chat**, two-layer fact and reusable-experience memory for **Working**, and version-evolution diff-chain tracking for **Coding**. Built on top of Hy Memory, **[MemHub](memhub/README.md)** is a local-first desktop and CLI product that unifies conversation history and coding traces from user-authorized AI applications (such as Claude Code, Cursor, Codex, OpenCode, and Qwen Code) into a single managed runtime and local data directory, enabling governed cross-application memory recall.
+
+<div align="center">
+  <video src="https://github.com/user-attachments/assets/94405890-8429-47c2-9084-38f7ed9f126f" controls width="640"></video>
+  <p><b>MemHub Demo Video</b></p>
+</div>
+
+---
+
+## Latest News
+
+* *<mark>[new]</mark>* 🔥🔥🔥 **[2026-10]**: 🚀 **Released** **Hy Memory 2.0 (`hy-memory==2.0.1`)** on [PyPI](https://pypi.org/project/hy-memory/2.0.1/) and open-sourced the **Hy-Memory** monorepo together with **[MemHub](memhub/README.md)**!
+* *<mark>[new]</mark>* 🔥🔥🔥 **[2026-10]**: 🚀 **Open-sourced** **[Hy-Memory-30B-A3B](https://huggingface.co/tencent/Hy-Memory-30B-A3B)** on Hugging Face along with its [technical report](https://arxiv.org/abs/2610.22196) on attributed reinforcement learning for long-term memory writing!
+* *<mark>[new]</mark>* 🔥🔥 **[2026-09]**: 📊 **Released** **[CMB: A Coding Memory Benchmark for Long-Horizon and Interleaved Coding Agents](docs/papers/CMB_A_Coding_Memory_Benchmark_for_Long_Horizon_and_Interleaved_Coding_Agents.pdf)** (submitted to **ICLR 2027**).
+* *<mark>[new]</mark>* 🔥🔥 **[2026-08]**: 🎉 **Accepted** at **EMNLP 2026**: **[Memory Beyond Recall: A Dual-Process Cognitive Memory System for Self-Evolving LLM Agents](https://arxiv.org/abs/2606.09483)**!
+* 🔥 **[2026-05]**: 🌟 **Initial Release** Released **[Hy Memory 1.0](https://mp.weixin.qq.com/s/dH5PGpxqArFZkSq3-QxWYA)**, our first-generation dual-system cognitive memory framework for self-evolving LLM agents.
+
+---
+
+## Papers
+
+Welcome to the **Hy Memory Research Family**, covering cognitive chat memory, long-horizon coding memory, and RL-trained memory writing models:
+
+> [**Memory Beyond Recall: A Dual-Process Cognitive Memory System for Self-Evolving LLM Agents**](https://arxiv.org/abs/2606.09483) *(Accepted at **EMNLP 2026**)*  
+> **TL;DR:** Proposes the dual-process (System 1 + System 2) cognitive memory architecture for **Chat**, organizing personal memory into an 8-layer hierarchy (raw dialogues, atomic facts, summaries, schemas, and prospective intentions) with conflict reconciliation and cross-domain schema induction.  
+> 📄 Paper: https://arxiv.org/abs/2606.09483
+
+> [**CMB: A Coding Memory Benchmark for Long-Horizon and Interleaved Coding Agents**](docs/papers/CMB_A_Coding_Memory_Benchmark_for_Long_Horizon_and_Interleaved_Coding_Agents.pdf) *(Submitted to **ICLR 2027**)*  
+> **TL;DR:** Introduces a benchmark and two-layer + version-evolution diff-chain memory method for long-horizon **Coding** agents, preserving both reusable engineering experiences and exact code revision trajectories across interleaved tasks.  
+> 📄 Paper: [docs/papers/CMB_A_Coding_Memory_Benchmark_for_Long_Horizon_and_Interleaved_Coding_Agents.pdf](docs/papers/CMB_A_Coding_Memory_Benchmark_for_Long_Horizon_and_Interleaved_Coding_Agents.pdf)
+
+> [**Hy-Memory-30B-A3B: Attributed Reinforcement Learning for Long-Term Memory Writing**](https://arxiv.org/abs/2610.22196) *(Open Model Technical Report)*  
+> **TL;DR:** Trains a 30B-A3B MoE model via attributed reinforcement learning specifically for high-precision long-term memory extraction and conflict reconciliation.  
+> 📄 Paper: https://arxiv.org/abs/2610.22196 · Model: https://huggingface.co/tencent/Hy-Memory-30B-A3B
+
+---
+
+## Quick Start
+
+### 1. Installation
+
+```bash
+pip install hy-memory==2.0.1              # core (includes ChromaDB and Kuzu)
+pip install "hy-memory[qdrant]==2.0.1"    # + Qdrant
+pip install "hy-memory[faiss]==2.0.1"     # + FAISS
+pip install "hy-memory[graph]==2.0.1"     # + Neo4j
+pip install "hy-memory[mysql]==2.0.1"     # + MySQL cache
+pip install "hy-memory[rerank]==2.0.1"    # + local multilingual cross-encoder rerank
+pip install "hy-memory[all]==2.0.1"       # everything
+```
+
+### 2. Configuration
+
+Only an LLM and an embedding endpoint are needed; any OpenAI-compatible service works:
+
+```bash
+export MEMORY_LLM_API_KEY="sk-your-key"
+export MEMORY_LLM_BASE_URL="https://api.deepseek.com"
+export MEMORY_LLM_MODEL="deepseek-chat"
+
+export MEMORY_EMBEDDER_API_KEY="sk-your-key"
+export MEMORY_EMBEDDER_BASE_URL="https://dashscope.aliyuncs.com/compatible-mode/v1"
+export MEMORY_EMBEDDER_MODEL="text-embedding-v3"
+export MEMORY_EMBEDDING_DIMS=1024
+```
+
+Or use the OpenAI defaults with a single key:
+
+```bash
+export OPENAI_API_KEY="sk-your-key"
+```
+
+See the [Environment Variable Reference](docs/env_reference.md) for the full list.
+
+### 3. Chat Memory
+
+```python
+from hy_memory import HyMemoryClient
+
+client = HyMemoryClient(mode="pro")
+
+# Write: plain text or OpenAI-format messages
+client.add("I love sci-fi movies, especially Interstellar", user_id="user_1")
+client.add([
+    {"role": "user", "content": "Recommend a movie"},
+    {"role": "assistant", "content": "Try Interstellar — a sci-fi masterpiece by Nolan"},
+], user_id="user_1")
+
+# Search: returns the profile / normal / proactive channels
+results = client.search("What movies does the user like?", user_ids=["user_1"], limit=10)
+for mem in results["memories"]["normal"]:
+    print(f"  [{mem['score']:.2f}] {mem['content']}")
+
+client.close()
+```
+
+### 4. Working & Coding Memory
+
+Writes must include a tool-call trace (`tool_calls` or `role="tool"` messages) and take effect in `pro` / `ultra` mode only (`lite` ignores `scene` and stores everything as raw memory):
+
+```python
+messages = [
+    {"role": "user", "content": "Fix the timeout in the search client."},
+    {"role": "assistant", "content": "", "tool_calls": [{
+        "id": "call_1", "type": "function",
+        "function": {"name": "apply_patch", "arguments": '{"path":"src/search.py"}'},
+    }]},
+    {"role": "tool", "tool_call_id": "call_1", "name": "apply_patch",
+     "content": "Patch applied successfully"},
+]
+
+client.add(
+    messages,
+    scene="coding",                              # or "working"
+    user_id="user_123",
+    workspace_id="github.com/example/service",   # optional: isolate by repository / project
+    branch="fix/search-timeout",                 # optional: requires workspace_id
+)
+
+result = client.search(
+    "Which timeout implementation was finally kept?",
+    scene="coding",
+    user_ids=["user_123"],
+    workspace_id="github.com/example/service",
+    branch="fix/search-timeout",
+    limit=5,
+)
+
+result["facts"]          # fact layer
+result["experiences"]    # experience layer
+result["chain_block"]    # coding only: version-evolution context
+```
+
+### 5. Routing, Source Isolation & Advanced APIs
+
+- **Automatic scene routing**: When `scene` is omitted, writes without tool calls go straight to `chat` (zero LLM calls), and writes with tool calls are classified once into `chat` / `working` / `coding`. For searches, `search_mode="default"` goes to `chat` with zero LLM calls, while `search_mode="agentic"` performs scene classification, query rewriting, and time-range parsing. See [Working/Coding Scenes](docs/scene_coding_usage.md).
+- **Separate memories by source**: Pass `source="openclaw" | "cursor" | "codex"` on `add()` and filter with `include_sources` / `exclude_sources` on `search()` to isolate caller applications independently of `agent_id`.
+- **CRUD & System 2 evolution**: `client.get(id)`, `client.update(id, text)`, `client.delete(id)`, `client.list_memories(user_id=...)`, and `client.evolve(user_id=...)` (triggers System 2 in `ultra` mode).
+- **Per-call embedding endpoint override**: Pass `embed_override={"base_url": ..., "api_key": ...}` to `add()` / `search()` or use `with embed_endpoint_override(...):` for concurrency-safe endpoint switching.
+
+For provider configuration, storage backends, scenes, and the complete API, see the [Usage Guide](docs/usage.md).
+
+---
+
+## System Architecture
+
+<div align="center">
+  <img src="docs/images/architecture.svg" alt="Hy Memory architecture" width="95%">
+</div>
+
+Hy Memory provides three memory scenes (`scene`), one per kind of task. `add()` / `search()` go through the scene router first, then into the Chat or the Working / Coding pipeline (orange parts in the diagram are coding-only; without them the pipeline is Working):
+
+| `scene` | Tasks | Memory shape |
+|---|---|---|
+| `chat` | Small talk, personal information, preferences, general Q&A | Hierarchical memory (L0–L7) |
+| `working` | Productivity work: documents, spreadsheets, research, financial analysis, content creation, computer operation | Two-layer memory: session facts + reusable experiences |
+| `coding` | Software engineering: coding, debugging, testing, builds, APIs/SDKs, scripts, SQL | The same two-layer memory as `working`, plus a code version-evolution chain (diff chain) |
+
+### 1. Chat: Memory Hierarchy
+
+For long-term personal memory. Raw conversations are abstracted layer by layer into facts, summaries, a profile, and higher-level cognitive structures:
+
+| Layer | Name | Content |
+|---|---|---|
+| L0 | `BASIC_INFO` | Basic information |
+| L1 | `RAW` | Raw conversation (append-only) |
+| L2 | `FACT` | Atomic facts (versioned, immutable records) |
+| L3 | `SUMMARY` | Session summaries |
+| L4 | `IDENTITY` | Reserved |
+| L5 | `KNOWLEDGE` | Reserved |
+| L6 | `SCHEMA` | Mental models (abstract narrative templates, graph layer) |
+| L7 | `INTENTION` | Prospective intentions (with an expiry; demoted to ordinary facts once expired) |
+
+**Modes**
+
+| Mode | What it does | Graph DB | Use case |
+|------|--------------|----------|----------|
+| `lite` | Raw-only embedding writes and searches, no LLM calls; `scene` and `layers` are ignored | No | Vanilla vector RAG, fast ingestion, zero LLM cost |
+| `pro` | + LLM extraction + reconcile | Optional (`MEMORY_ENABLE_GRAPH`, off by default) | Standard workloads |
+| `ultra` | + System 2 schema induction + cross-domain sweeper (triggered by `evolve()`) | Yes (always on) | Full cognitive architecture |
+
+### 2. Working: Two-Layer Productivity Memory
+
+For getting things done. One session with tool calls (a trace) produces both layers at once:
+
+| Layer | What it records | Per session | Structure |
+|---|---|---|---|
+| **Facts** (`WorkingFact`) | What this session did: the task, the approach, the result | Exactly 1, no threshold | `statement`, `subject`, `files`, `details` (verbatim source) |
+| **Experiences** | Approaches that can be reused next time a similar task comes up | 0–N, must pass a value threshold | `task`, `search_keys`, `solution`, `boundary_envs`, `confidence` |
+
+The fact layer guarantees that work which was done is remembered; the experience layer makes what was learned reusable. The two layers link to each other (`fact.derived_experience_ids` ↔ `experience.source_fact_ids`), and superseded facts stay traceable through a task-progress chain (`fact_chain_summary`).
+
+### 3. Coding: Two-Layer Memory + Version-Evolution Chain
+
+Coding **reuses the same two-layer pipeline and data schema** as Working. It differs in three ways:
+
+| | Working | Coding |
+|---|---|---|
+| **Extraction spec** | Productivity-task spec | Software-engineering spec: the subject must be code or a decision; record exact coordinates (file / function / branch) instead of pasting code |
+| **Storage** | `coding_memory.db` + `*_coding_keys` / `*_working_facts` collections | `coding_memory_cv.db` + `*_cv` collections, fully isolated from working |
+| **Version-evolution chain** | None | **Yes**: how many times the same code was changed, and what each change was |
+
+**Why a version-evolution chain**: fact extraction deliberately avoids pasting code (the budget goes to more informative coordinates), so a version that was later reverted never appears in a fact.
+That version is usually not in the working tree or at HEAD either, so it cannot be read back afterwards. The chain stores the real diff of every version with zero LLM calls, filling in exactly the information a summary inevitably drops.
+
+**Design highlights** (`hy_memory/coding/chain_store.py`):
+
+- **A decorator, not a retriever**: the vector layer decides which facts are returned; the chain only attaches, under each fact, every revision of the code it touches (the user's words for that revision + the real diff).
+- **Change sources**: local Git diffs (set `MEMORY_CODING_CHAIN_REPO_ROOT`), or deterministic replace actions with `path` / `old` / `new` in the tool trace.
+- **Chain granularity & isolation**: one thread corresponds to one block of one function in one file on one branch, isolated by `user_id` + `workspace_id`.
+
+---
+
+## Support
+
+### Storage Backends
+
+- Vector stores: ChromaDB (default), Qdrant, FAISS
+- Graph stores (ultra mode): Kuzu (default), Neo4j
+- Working / Coding metadata: local SQLite
+
+### Documentation
+
+- [Usage guide](docs/usage.md) — full configuration reference, API details, deployment modes
+- [Environment variables](docs/env_reference.md) — settings and defaults
+- [Search and Reader guide](docs/hy_memory_search_skill.md) — reader selection, schema quotas, rerank, and return channels
+- [Working/Coding Scenes](docs/scene_coding_usage.md) — productivity-memory routing, response shapes, and coding chain behavior
+- [Graph memory design](docs/pro_graph_design.md) — graph projection, rerank, relation paths, and deployment limits
+- [Environment template](.env.example) — a copy-ready configuration template
+- [MemHub README](memhub/README.md) — local-first desktop & CLI product overview, runtime commands, and privacy boundaries
+- [OpenClaw plugin](plugins/openclaw/README.md) — agent integrations live under `plugins/` (overview: [plugins/README.md](plugins/README.md))
+
+### License
+
+Hy-Memory is licensed under Apache-2.0. See [LICENSE](LICENSE); third-party
+components remain subject to their respective licenses and notices.